Dear Jonathan, a few things in random order: -1- 1G permsize? Do you really need it? -2- 64MB is not the memory that GeoServer will use for a single request (the total one I mean). It imposes a limit on the backbuffer on which geoserver will render, hence it is an indirect limitation to the size of the image one can request (#bands*w*h tells you the size of the backbuffer in bytes)
This means that depending on the underlying data as well as on the style it can use much more memory. Aside, memory is not released instantaneously hence under load unless you put control flow in the mix you might still get OOM errros -3- put XMX == XMS there is no point on a server application to set them differently it will simply make it easier to fragment heap memory and make OOM easier ti happen. There is more but this is just a braing dumpo of obvious things. Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. On Tue, Mar 8, 2016 at 1:48 PM, Jonathan Moules <jonathan-li...@lightpear.com> wrote: > So I doubled the XMX to 12G and sure enough it can now handle 8 threads with > no problems. > > But curiously, I then restarted the instance again (to throw in a second > instance) but the very first request returned: > > Rendering process failed > java.lang.OutOfMemoryError: Java heap space > Java heap space > > I've seen this during a few of my tests - the first request (sometimes first > several) somehow comes back as being memory constrained, even though there > are/should be no demands on GeoServer when it's received. > Is this normal? > Cheers, > Jonathan > > > > ---- On Tue, 08 Mar 2016 11:31:43 +0000 <jonathan-li...@lightpear.com> wrote > ---- > > Hi List, > I'm experiencing some memory issues with GeoServer 2.7.1 on Linux. The > startup settings are: > jvm_opts=-Xms2G -Xmx6G -XX:MaxPermSize=1024m (So 6GB of Heap). > > I'm running some JMeter tests to make requests like this: > > http://localhost:8080/geoserver/wms?LAYERS=myayer&FORMAT=image%2Fpng8&TRANSPARENT=TRUE&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG%3A27700&BBOX=404453,555869,415688,572175&WIDTH=3210&HEIGHT=4659&FORMAT_OPTIONS=dpi:300 > > As you can see, it's for a very large image: 3210 * 4659 at 300DPI (A3 > printing size; alas we cannot use tiles). While mostly targetted at rural > areas there are some towns in the given areas, so well into the 10's of > thousands of features sometimes hundreds of thousands. The data is coming > from Oracle. > WMS "Max rendering memory (KB)" is at 64MB (the default); I've increased > rendering time to be up to 5 mins (the max is taking about 100 seconds). > > Using 5 threads in Jmeter against one instance and running tests against > lots of different scales we're seeing a probably 10-20% of requests return: > > <ServiceException code="internalError"> > Rendering process failed > java.lang.OutOfMemoryError: Java heap space > Java heap space > </ServiceException> > > > We've also had at least one of these: > > <ServiceException code="internalError"> > Rendering process failed > java.lang.OutOfMemoryError: GC overhead limit exceeded > GC overhead limit exceeded > </ServiceException> > > Given there are only 5 threads, and the max rendering memory is a mere 64MB, > even taking into account all the features that need to be loaded, we're > surprised that somehow Java is running out of space. Is it worth increasing > the -Xmx even higher? Is there anything else we can do to obviate this > problem? > Thanks, > Jonathan > > > > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://makebettercode.com/inteldaal-eval > _______________________________________________ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > ------------------------------------------------------------------------------ _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
