Hi Raplh, what I wanted to say is that memory is not always freed in the default VM settings. Otherwise hitting the "Garbage Collect" Button in the VM Monitor application wouldn't be able to free GBs of unused memory.
Chris -----Ursprüngliche Nachricht----- Von: Ralph Goers [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 11. Juli 2006 15:54 An: [email protected] Betreff: Re: AW: AW: OutOfMemoryError Christofer Dutz wrote: > > Hi Oleg > > Well exactly this is why I used JRockit, because I didnt want to > bother finding out how to tweak it ;) I know that the way the > Garbagecollector works can be configured using command-line > parameters, but I dont know which ones and if they have the desired > effect. > > I just wanted to give you the hint that you will not find any real > memory-leaks, because there arent any and that the problems you are > having result of a garbage collection problem in the VM realizing > this earlier would have made many many days of code-checking and > profiling obsolete L > > Good luck, > > Chris > I have to disagree. While you may not find any memory leaks, profiling should always be recommended. First, it helps you understand how your application operates. Second, you may find that you have pool sizes that are too low or that you need to modify some pipelines or make some other modifications. However, we have found significant improvements by modifying the JVM settings. Unfortunately, I don't have them in front of me at the moment. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
