On Thu, Oct 4, 2012 at 11:06 AM, Robert Buckley
<robertdbuckley@anonymised.com> wrote:
Hi,
i`m installing geoserver in tomcat7 on an Ubuntu 12.04 Server with only
512mb RAM
This all went fine, but now tomcat7 crashes even before geoserver can be
started. Simply a matter of memory.
I have set the max/min PermGen to 512 and Xms /Xmx also to 512.
Is there any possible way to run geoserver on so little memory?
thanks for any tips or tricks
Robert
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
I am aware of the production environment settings. I also know that it is recommended to use 1gb upwards of RAM.
I was looking for a few tips or tricks regarding running in a sub-optimal environment. I have set tomcat7 JAVA_OPTS as written in the production documentation
but geoserver still crashes after a few seconds.
INFO: validateJarFile(/var/lib/tomcat7/webapps/geoserver/WEB-INF/lib/servlet-api-2.5.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
04 Oct 06:51:29 WARN [config.CustomEditorConfigurer] - Passing PropertyEditor instances into CustomEditorConfigurer is deprecated: use PropertyEditorRegistrars or PropertyEditor class names instead. Offending key [org.geotools.util.Version; offending editor instance: org.geoserver.platform.util.VersionPropertyEditor@anonymised.com
Oct 04, 2012 6:51:30 AM org.geoserver.platform.GeoServerExtensions checkContext
SEVERE: Extension lookup occured, but ApplicationContext is unset.
04 Oct 06:51:30 ERROR [geoserver.global] -
i`m installing geoserver in tomcat7 on an Ubuntu 12.04 Server with only
512mb RAM
This all went fine, but now tomcat7 crashes even before geoserver can be
started. Simply a matter of memory.
I have set the max/min PermGen to 512 and Xms /Xmx also to 512.
Is there any possible way to run geoserver on so little memory?
thanks for any tips or tricks
Robert
Don’t let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
first remove every service you do not need, no WPS, no format that you do
not access, only datbases you need try to make the installation as lean as
possible.
Next starting with 128 MB PermGen/MaxPermGen, (may be even 96 MB) and go up
in 32MB steps, if 128 does not suffice. Try to minimise the PermGen. Give as
much as you can to the heap.
There was a link on this list from somebody pointing to: http://opengeo.org/publications/geoserver-production/
which is a nice summary of geoserver configuration for production.
Then monitor the memory use of the VM :
-Xloggc:somewhere\gc.log
-XX:+PrintGCDetails
I do appreciate the sportsmanship of this attempt to get away with 512 MB
RAM, however, compared to the work involved isn't it cheaper to go to to the
next shop get some RAM and stuff it in the box?
Cheers
Christian
-----
____________________________
Dr Christian Maul
Project Manager
Information Services Branch
Department of Sustainability and Environment
Level13, Marland House, 570 Bourke Street
Melbourne 3000
You probably don’t need 512MB for PermGen. If I needed to run GeoServer in 512MB of RAM, I would start by setting JAVA_OPTS like: “-Xmx128M -XX:MaxPermSize=192M” and reducing the size of the Tomcat thread pool (to limit the number of concurrent requests GeoServer will try to serve. You can also do this in a more fine-grained way with the control-flow module: http://docs.geoserver.org/stable/en/user/extensions/controlflow/index.html, but that would be adding more code and contributing to the pressure on PermGen.)
first remove every service you do not need, no WPS, no format that you do
not access, only datbases you need try to make the installation as lean as
possible.
Next starting with 128 MB PermGen/MaxPermGen, (may be even 96 MB) and go up
in 32MB steps, if 128 does not suffice. Try to minimise the PermGen. Give as
much as you can to the heap.
There was a link on this list from somebody pointing to: http://opengeo.org/publications/geoserver-production/
which is a nice summary of geoserver configuration for production.
Then monitor the memory use of the VM :
-Xloggc:somewhere\gc.log
-XX:+PrintGCDetails
I do appreciate the sportsmanship of this attempt to get away with 512 MB
RAM, however, compared to the work involved isn’t it cheaper to go to to the
next shop get some RAM and stuff it in the box?
Cheers
Christian
Dr Christian Maul
Project Manager
Information Services Branch
Department of Sustainability and Environment
Level13, Marland House, 570 Bourke Street
Melbourne 3000
Don’t let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev