How do the amount of available memory and the JDK memory settings (eg Xms512M -Xmx512M) relate? Having 512MB in my server, what's the maximum i can/should set these parameter so i'm not starving the other processes of memory?
Any real-life thoughts? (I'll start googling this anyway) Jorg
Arje Cahn wrote:
By the way, i've set up http://wiki.cocoondev.org/Wiki.jsp?page=CocoonPerformance to scribble down some performance tricks. Please add your findings!
Arj�
-----Original Message-----
From: Arje Cahn Posted At: Monday, January 26, 2004 1:26 PM
Posted To: Cocoon Dev List
Conversation: JVM memory settings for production Cocoon?
Subject: RE: JVM memory settings for production Cocoon?
Hi,
We have Xms & Xmx both on 512mb for about 3 or 4 medium websites (about 10 to 20.000 pages in total).
Make sure you set the "maxobjects" of the transient-store to a high number if you've got lots of memory available. It's set to 100 by default which is *way* too low. I use about 4 to 8000. Seems to work. Check the status page to use if it's not overloading.
Also, set the store-janitor's heapsize in cocoon.xconf higher (by default it's set to use only 64 mb). Set the use-store attribute of the XSLT processor you're using to true to cache your XSLT's (is this still set to false by default http://archives.real-time.com/pipermail/cocoon-devel/2003-Octo
ber/022203.html?). Turn off subsitemap reloading (only for deployment!).
Oh, use XSLTC.
Hope this helps!
Arj�
-----Original Message----- From: Rottmann, Lars [mailto:[EMAIL PROTECTED] Posted At: Monday, January 26, 2004 11:44 AM Posted To: Cocoon Dev List Conversation: JVM memory settings for production Cocoon? Subject: AW: JVM memory settings for production Cocoon?
We currently use the following options (on a 4GB machine):
JAVA_OPTIONS_GENERAL="-server -Djava.awt.headless=true \ -Xms2536M -Xmx2536M -XX:+UseParallelGC \ -XX:+UseAdaptiveSizePolicy -DisableExplicitGC "
Lars
On 23.01.2004 17:06, Andrzej Jan Taramina wrote:
Currently have -Xms set to 256MB and -Xmx set to 512MB, but that sounds low
to me.
Not that I'm very experienced with such settings, but I
"heard" that
setting Xms and Xmx to the same value is recommendable and it was standard in the company I worked for. 256 MB is indeed not
much, but 512
should be enough for normal Cocoon pipeline processing.
Using FOP or
Batik is more memory consuming.
Joerg
Vodafone Global Content Services Limited Registered Office: Vodafone House, The Connection, Newbury, Berkshire RG14 2FN
Registered in England No. 4064873
This e-mail is for the addressee(s) only. If you are not an addressee, you
must not distribute, disclose, copy, use or rely on this
e-mail or its
contents, and you must immediately notify the sender and delete this e-mail
and all copies from your system. Any unauthorised use may be unlawful. The
information contained in this e-mail is confidential and may also be legally
privileged.
