[opencms] [opencms-dev] Optimizing OpenCMS performance.

[Jonathan Woods]

I'd have meant 'debug output' - i.e. setting log4j debug levels every to
INFO or WARN, and reducing mod_rewrite/mod_jk logging (if you're using those
modules).

-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Nigel Kersten
Sent: 16 June 2006 06:23
To: The OpenCms mailing list
Subject: Re: [opencms] [opencms-dev] Optimizing OpenCMS performance.


On 15/06/2006, at 9:52 PM, Jorge Gonzalez wrote:

> Another easy thing to improve performance: cut off all the trace 
> output on the production server.

What do you mean by this exactly? Do you mean disabling allowTrace in the
relevant Connector?

--
Nigel Kersten [Senior Technical Officer] College of Fine Arts, University of
NSW, Australia.
CRICOS Provider Code: 00098G




_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev