On Mon, Apr 30, 2012 at 6:23 PM, Gabriel Roldan <[email protected]> wrote:
> Actually it is not exaggerated. I can make it go OOM with 25K layers
> (not 200K), 2GB heap size, and 20 concurrent GetCapabilities requests.
> Try the following for yourself, from the GSIP69 branch
> <https://github.com/groldan/geoserver/tree/GSIP69> (finally managed to
> redo it with squashed commits where the system builds ok on each one,
> the old branch is still there for reference, called GSIP69_old):
>
Read it all, interesting points. Not much to add, I guess my understanding
of where the memory is spent in the in memory catalog is missing some
important bit, the usage you're found seems really a lot to me... but
numbers
are numbers.
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
-------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
