Plumbr Java Performance Survey
308 respondents, out of which 73% were software engineers, described their experience with detecting and solving Java performance issues.
3 key findings
- The average time that is spent on finding and fixing the root cause is 80 hours
- It takes approximately 2 weeks to solve a Java performance issue
- 76% of the respondents struggle the most with “trying to reproduce – gather evidence – make sense of the evidence – link evidence to the root cause” cycle
We like to call it the Ultimate Handbook of java.lang.OutOfMemoryErrors. It’s a 28-page e-book of explanations, code examples and solution guidelines for everything related to java.lang.OutOfMemoryError exceptions.
The 8 symptoms of java.lang.OutOfMemoryError covered:
- java.lang.OutOfMemoryError: Java heap space
- java.lang.OutOfMemoryError: GC overhead limit exceeded
- java.lang.OutOfMemoryError: Permgen space
- java.lang.OutOfMemoryError: Metaspace
- java.lang.OutOfMemoryError: Unable to create new native thread
- java.lang.OutOfMemoryError: Out of swap space?
- java.lang.OutOfMemoryError: Requested array size exceeds VM limit
- Out of memory: Kill process or sacrifice child
Java Garbage Collection Handbook
Plumbr engineers know the JVM inside out. However, not everyone has the luck to spend their days waist-deep inside the GC clockwork. Those of you – the unlucky ones 😉 – need to rely more on educational content. We believe our concise and illustrated handbook is one of the best ways to get yourself acquainted with JVM garbage collection.
Table of contents:
- What Is Garbage Collection?
- Garbage Collection in Java
- GC Algorithms: the Basics
- GC Algorithms: the Implementations
- GC Tuning
- GC Tuning: Tooling
- GC Tuning: Advanced