We are running the Globus WSRF Container. It is taking >300 MB of
resident memory and 1.5 GB of virtual memory. This seems extremely
high. Can anyone comment on methods to limit the memory consumption of
the container? Below are top and ps traces. FWIW, we're also running
Tomcat 5.5. Could we be running the Globus components from inside this,
instead of via its own ServiceContainer on a different port?
TIA, Ian
top:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4709 globus 18 0 1551m 300m 3120 S 2.0 7.6 168:33.51 java
ps:
globus 4709 1 0 Oct11 ? 02:48:34
/opt/osg-local/ce-1.0/jdk1.6/bin/java
-Dlog4j.configuration=container-log4j.properties -Xms256M -Xmx1024M
-Dorg.globus.wsrf.container.persistence.dir=/opt/osg-local/ce-1.0/vdt-app-data/globus/persisted
-DGLOBUS_LOCATION=/opt/osg-local/ce-1.0/globus
-Djava.endorsed.dirs=/opt/osg-local/ce-1.0/globus/endorsed
-DX509_CERT_DIR=/opt/osg-local/ce-1.0/globus/TRUSTED_CA
-Djava.security.egd=file:///dev/urandom -classpath
/opt/osg-local/ce-1.0/globus/lib/bootstrap.jar:/opt/osg-local/ce-1.0/globus/lib/cog-url.jar:/opt/osg-local/ce-1.0/globus/lib/axis-url.jar
org.globus.bootstrap.Bootstrap
org.globus.wsrf.container.ServiceContainer -p 9443
--
Ian Stokes-Rees, Research Associate
SBGrid, Harvard Medical School
http://sbgrid.org
