Java Developer Series - Quest Software

More documents

Recommendations

Info

Mastering Object Allocation Dangers • Two main threats to Java memory efficiency – Loitering Objects – Object Cycling You Can Expect More. • You have to understand the role of object references with respect to garbage collection in order to avoid these problems
Java Memory Management You Can Expect More. • As objects are created they’re stored within the JVM’s heap • They can only be removed in a JVM-controlled garbage collection – Removes objects that are no longer needed – Undecidable in general, so Java uses an approximation... • Removes objects that are no longer reachable (accessible to the program at the beginning of a garbage collection cycle) –The reachability test starts at the heap’s root set
Page 1 and 2: Java Developer Series - Part 1 - Bu
Page 3 and 4: About Quest Software You Can Expect
Page 5: Performance Challenges Facing the J
Page 9 and 10: Dynamic Nature of the Root Set - 1
Page 11 and 12: Dynamic Nature of the Root Set - 3
Page 13 and 14: Garbage Collection and Object Reach
Page 15 and 16: Garbage Collection and Object Reach
Page 17 and 18: What is a “Memory Leak” in Java
Page 19 and 20: Reference Management You Can Expect
Page 21 and 22: Design for Reference Management •
Page 23 and 24: Heap Analysis - List of Objects & R
Page 25 and 26: Avoid Object Cycling • Performanc
Page 27 and 28: Avoiding Performance "Gotchas" in D
Page 29 and 30: Excessive EJB-Related SQL Execution
Page 31 and 32: Strategies for Guaranteeing Perform
Page 33 and 34: Test Throughout The Cycle You Can E
Page 35 and 36: Dealing With Outsourcing You Can Ex
Page 37 and 38: What Is JProbe ® Suite? You Can Ex
Page 39 and 40: Summary • Performance begins in D

Java Developer Series - Quest Software

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?