Comentários (3)

1 edwin11 comentou às Link permanente

Yes, the GC logging is very important, especially when testing a long-running application.

 
Here are some basic tips on how to interpret the logs, as well as (very) basic tuning possibilities: http://hello-world-2-0.blogspot.com/2008/04/tuning-java-garbage-collection.html. Hope it helps.

2 Tom.Seelbach comentou às Link permanente

Hi Chris,
This is still good advice today! I ran into a case today (working Level 3 for WebSphere) where a production system isn't performing properly and verbose gc is NOT enabled. We have no way to know if GC/memory is a factor. It would be good if you can re-emphasis that turning on verboseGC from the beginning in production is the smartest way to go. The overhead is low and the data is there when you need it. Don't wait for a system down situation to turn it on.
thanks,
Tom

3 Chris Bailey IBM comentou às Link permanente

I've got some updated performance numbers for verbose:gc based on more formal benchmarks here (slide 17):
http://www.slideshare.net/cnbailey/websphere-technical-university-introduction-to-java-diagnostic-tools

 
This measures it at 0.1289% for a highly loaded system

Incluir um Comentário Incluir um Comentário