Hi! We are currently evaluating batikserver+batik 1.6 (http://www.gocept.com/open_source_software/BatikServer) to save the time the virtual machine needs to start up when converting SVGs.
Unfortunately the memory usage of this service is rather evil: (each line covers the relevant memory columns of ps avx) 1st request: 3 55 246168 32392 2nd request: 3 55 245912 35136 3rd request: 3 55 245912 36108 somehow the mem is never really freed and slowly (but constantly). When doing this after a night without any requests it consumed up to 60 MB (last column) and this is simply not acceptable and proved (to me at least :P) that it is really never freed. Somehow the garbage collection doesn't really work. The garbage collection only starts to clean the objects when the server is stopped. Even when i lowered the allowed memory for java so that it can just handle one request it did one request and then failed with an out of memory request. We have seen this behaviour when reloading squiggle again and again too so this must somehow be either a java or a batik problem. Does anybody have a hint on what is going on? Is this a batik bug? Or are there any switches for java which could help? Kind regards, Andreas Streichardt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
