Are Your Garbage Collection Logs Speaking to You?

It's common knowledge that tuning the JVM's heap size and choice of collector can have a major impact on the performance of your application. What isn't generally known is that even with a heap larger than needed, your JVM can still be starved for memory. This session examines how to use garbage collection logs to diagnose missizing and then looks at rightsizing the JVM's various memory pools so that you can get most out of your application. The session also covers critical memory conditions that can be fixed—or best fixed—only by altering application code.

Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the "Materials"). The Materials are provided "as is" without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.