Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <50460.10.0.0.1.1039482326.squirrel@_default_>
Date: Mon, 9 Dec 2002 19:05:26 -0600 (CST)
Subject: Re: Cocoon performance tuning
From: "Antonio Gallardo" <agallardo@agsoftware.dnsalias.com>
To: <cocoon-dev@xml.apache.org>
In-Reply-To: <3DF53894.7000304@apache.org>
References: <20021208132053.GB14122@testbox.incap.ru>
        <3DF38B1E.50703@geekspeak.org>
        <3DF456FB.7060304@outerthought.org>
        <3DF53894.7000304@apache.org>
Importance: Normal
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I agree since developers always will read more info about how to "get
started development with Cocoon". Then there can be a document that will
explain how to turn on the developer stuff.

Antonio Gallardo.

Stefano Mazzocchi dijo:
> Steven Noels wrote:
>
>>> Big point is setting log thresholds to ERROR (instead of INFO or
>>> DEBUG). This should give an immediate and dramatic performance gain.
>>
>>
>> How about setting these to ERROR by default?
>
> Yeah, on Cocoon 2.0.x we should try to make an effort to make a fast
> cocoon ready right out of the box, people can turn on debugging if they
> want to.
>
> What do you think?
>
> --
> Stefano Mazzocchi                               <stefano@apache.org>
> --------------------------------------------------------------------
>
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org