When would you care about G1 versus ZGC in a latency-sensitive Java service?
PICTURE THIS: HOW JAVA RUNS
Simple meaning
G1 is the common default: good throughput with pause goals in tens of milliseconds at moderate heaps.
WHY — JVM instead of guessing?
Why interviewers care about JVM:
contrast on JVM, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1G1 is the common
default: good throughput with pause goals in tens of milliseconds at moderate heaps.
- 2ZGC targets sub-millisecond pauses
on large heaps by doing more work concurrently, at some throughput cost.
- 3You choose from p99
latency, heap size, and measured pause logs, not from a blog title.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
G1 is the common default: good throughput with pause goals in tens of milliseconds at moderate heaps. ZGC targets sub-millisecond pauses on large heaps by doing more work concurrently, at some throughput cost.