On Fri, Jan 27, 2012 at 8:50 PM, Gabriel Roldan <[email protected]> wrote: > > I will try with a profiling session later today. > > @Justin: any advice on what kind of care should be taken to minimize > the proliferation of XSDSchemaImpl and GridCoverageReader instances?
Normally too many XSDSchemaImpl (hundreds of MB, a few tens is unfortunately normal) is normally indication of a memory leak in the WFS/schema subsystem. GridCoverageReader are cached in ResourcePool, as opening them is expensive, however per se they do not hold much memory, if they do it's via the raster metadata, normally caused my many ill structured raster files, like large and striped geotiffs (no inner tiling structure). Bertrand, could you provide more details on your memory analysis? Do you have a memory dump we can look into, or the output of jmap, something like: jmap -histo:live <jvm pid> | head -25 Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 339 8844549 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
