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

[justin.spies at sbcglobal.net]

Nigel,
Having such a large VM configured can cause garbage collection issues, which lead to performance problems.  I'm not sure that is the problem here, however to find out, you can use the following VM options:

-verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Xloggc:"C:\garbage.log"


Obviously you'll want to change the -Xloggc: value to a file that matches one on your file system.  With as large of a VM as you have, it is possible that the system is causing long pauses to collect a large amount of garbage objects.  Look for entries where the system does a full garbage collection and note how long they take and how far apart they are spaced.

Sincerely,
Justin L. Spies

----- Original Message ----
From: Nigel Kersten <nigel at cofa.unsw.edu.au>
To: The OpenCms mailing list <opencms-dev at opencms.org>
Sent: Friday, June 16, 2006 1:22:43 AM
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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20060616/531c6f3e/attachment.htm>