Christian Catchpole wrote: > also note that big servers with collection problems could use the > concurrent collector. > > I believe that you should be able to get at the memory utilization stats which would give you an idea of when GC was going to run. However I think that a good round of heap tuning may go a long way to solving the long GC pause time.
First, look at promotion rates vs liveliness in tentured. If the liveliness in old is high, you've got a problem in your code and resizing heap spaces can help but.... If liveliness in old is low, you've got a problem with heap sizing and I would suggest adjusting young/survivor space sizings. If the problem is in the code, profile the system under load while using netbeans (visualvm) generations counts to find the offending classes and then adjust code to reduce lifespan. Devil is in the detals ;-) Regards, Kirk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
