Performance Tuning · interview question
Why is it risky to diagnose production latency from GC logs alone?
Multiple choiceHardchapter-14-curatedpremiumperformance-tuningstop-the-world
Answer and explanation
Correct answer
B. Latency might come from blocked or spinning threads, and GC logs do not show that execution detail
Why
GC logs explain collection behavior over time, but they do not tell you what threads are blocked on or which external resource is causing contention. Mature diagnosis correlates GC, heap, and thread evidence.
Test yourself on Performance Tuning
A free test with instant, explained results. No account needed.
More Performance Tuning questions
- In a system using the Z Garbage Collector (ZGC), what is a notable advantage compared to traditional Stop-The-World…
- How would you explain a common cause of a 'java.lang.OutOfMemoryError: Metaspace' error in a JVM application in an…
- How would you explain a key advantage of the Z Garbage Collector (ZGC) over traditional garbage collectors in an…
- CPU is pinned and requests are hanging. Which artifact tells you what threads are doing right now?
- What does the Z Garbage Collector (ZGC) mainly aim to achieve?
- In the context of JVM garbage collection, what is the main benefit of using the G1 Garbage Collector over traditional…