Hi,
I'm using geoserver 2.0 to serve the following data:
- approx. 1TB of ECW aerial image data as WMS
- approx. 10GB of OSM vectordata in a PostGIS DB as PNG (street overlay)
in the following configuration:
- Win2008 64 bit dual xeon (16 core) with 16GB ram
Java configuration:
-XX:+HeapDumpOnOutOfMemoryError
-XX:MaxPermSize=256m
-Xmx1300M
-server
(I'm not using -XX:+UseConcMarkSweepGC and -XX:+CMSClassUnloadingEnabled
because this seems to slow down wms requests significantly)
JAI settings:
Memory Capacity: 0.8
Memory Threshold: 0.75
Tile Threads: 15
Tile Threads Priority: 8
Tile recycling switched on
Image I/O caching switched on
JPEG Native Acceleration switched on
PNG Native Acceleration switched on
Mosaic Native Acceleration swtiched on
Average WMS requests per second: 10
Average resolution of a WMS request: 800x600 pixels.
Approx. one time per day I'm getting a GC overhead limit exceeded.
(In the past I got much more 'out of memory' exceptions but that seemed to
be caused by using the 'dashed-line' SLD option for rendering the OSM data.
After removing this (is this a known problem in Geoserver 2.0?) it got much
better)
I've analyzed the hprof file using Eclipse Memory Analyzer which gives me
the following message:
One instance of *"javax.media.jai.RecyclingTileFactory"* loaded by
*"sun.misc.Launcher$ExtClassLoader
@ 0x14ba07d8"* occupies *1.044.494.000 (83,03%)* bytes. The instance is
referenced by
*it.geosolutions.imageio.imageioimpl.imagereadmt.ImageReadOpImageMT
@ 0x5de81358* , loaded by *"GeoServer"*. The memory is accumulated in one
instance of *"java.util.HashMap$Entry[]"* loaded by *"<system class loader>"
*.
*Keywords*
sun.misc.Launcher$ExtClassLoader @ 0x14ba07d8
java.util.HashMap$Entry[]
javax.media.jai.RecyclingTileFactory
GeoServer
This is not really surprising because i've enabled Tile recycling and a
memory capacity of 0.8
Couple of questions here:
- Am I using the correct settings? (Should tile recycling be switched off?)
- Would this option help me? -XX:-UseGCOverheadLimit
- Could there be a memory leak in the 'other' 20% of the allocated memory?
Thanks.
Regards,
Sjoerd Brandsma
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
