Hello Girish,
These is the Tomcat config that works nicely on a slightly smaller
(Win2008/8GB RAM/6 cores VM) server:
-Dcatalina.home=C:\Tomcat 6.0.35
-Dcatalina.log=C:\logs
-Dcatalina.base=C:\Tomcat 6.0.35
-Djava.endorsed.dirs=C:\Tomcat 6.0.35\endorsed
-Djava.io.tmpdir=C:\Tomcat 6.0.35\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=C:\Tomcat 6.0.35\conf\logging.properties
-Dcom.sun.management.jmxremote.port=xxxxxxx <--a number here
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false <--only if your server is
behind a firewall
-XX:PermSize=192m
-XX:MaxPermSize=512m
-XX:NewSize=900m
-XX:MaxNewSize=2700m
-XX:SurvivorRatio=6
-Xmx=4048 <-- but that is entered in a menu (Tomcat is running as a
service)
our major garbage collections are 300- 500msec, minor between 50 and 200
msec with this config.
Despite so-called parallel garbage collection and assurances to the
contrary, Java isn't doing a lot during garbage collection, so you need to
strike a balance between quantity and duration of minor and full garbage
collections. The configuration above is rather on the side of fewer and
longer garbage collections.
Try with that configuration above and try to improve and adapt it better to
your server.
Check you real usage with jvisualvm.exe (in the java bin directory- see
jmxremote params) as big unused memory spaces do not make your server
faster.
Further reading:
http://docs.oracle.com/cd/E13209_01/wlcp/wlss30/configwlss/jvmgc.html
Cheers
Christian
-----
____________________________
Dr Christian Maul
Project Manager
Information Services Branch
Department of Sustainability and Environment
Level13, Marland House, 570 Bourke Street
Melbourne 3000
PO Box 500, East Melbourne Vic 3002
Telephone: +61-3-8636 2325
Telefax: +61-3-8636 2813
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/Geoserver-performing-Slow-tp5023312p5023374.html
Sent from the GeoServer - User mailing list archive at Nabble.com.