Backend interview prep

Start

Java Serial GC vs Parallel GC Interview Questions and Answers | JVM Garbage Collection | Production Scenarios

Master Java Serial GC and Parallel GC with real interview questions, JVM internals, memory diagrams, production examples, tuning options, Stop-The-World events, and best practices.

Introduction

The Java Virtual Machine (JVM) provides multiple Garbage Collectors, each designed for different workloads.

The first collectors every Java developer should understand are:

  • Serial Garbage Collector
  • Parallel Garbage Collector (Throughput Collector)

Although modern applications commonly use G1GC, interviewers frequently ask about Serial and Parallel GC because they explain the evolution of Java Garbage Collection.

Understanding these collectors helps explain:

  • Stop-The-World (STW)
  • Throughput
  • Latency
  • Multi-threaded GC
  • Heap management
  • JVM tuning

These questions are commonly asked in Java, Spring Boot, Microservices, and Performance Engineering interviews.

Learning Objectives

After completing this article, you'll understand:

  • Serial Garbage Collector
  • Parallel Garbage Collector
  • Internal Architecture
  • Stop-The-World
  • Throughput
  • JVM Options
  • Minor GC
  • Full GC
  • Performance Characteristics
  • Production Scenarios
  • Frequently Asked Interview Questions

Evolution of Java Garbage Collectors

Java Version Default Collector
Java 1.2 Serial GC
Java 5 Parallel GC
Java 9+ G1GC

Serial Garbage Collector

Serial GC is the simplest Garbage Collector.

It performs all Garbage Collection work using a single GC thread.

During collection:

  • All application threads stop.
  • One GC thread performs collection.
  • Application resumes after completion.

Serial GC Architecture

flowchart LR

ApplicationThreads["Application Threads"] --> StoptheworldSingleGcThread["Stop-The-World --> Single GC Thread --> Young Generation --> Old Generation --> Application Resumes"]

Characteristics of Serial GC

  • Single-threaded GC
  • Stop-The-World pauses
  • Simple implementation
  • Small memory footprint
  • Suitable for small applications

Enabling Serial GC

java -XX:+UseSerialGC Application

Verify:

java -XX:+PrintCommandLineFlags -version

Parallel Garbage Collector

Parallel GC is also called the Throughput Collector.

Unlike Serial GC, it uses multiple GC threads.

Application threads still stop during collection, but several GC threads perform the work simultaneously.

This significantly improves throughput on multi-core CPUs.

Parallel GC Architecture

flowchart LR

ApplicationThreads["Application Threads"] --> StoptheworldGcThread1["Stop-The-World --> GC Thread 1"]

GcThread1["GC Thread 1"] --> YoungGeneration["Young Generation"]

ApplicationThreads["Application Threads"] --> GcThread2["GC Thread 2"]

GcThread2["GC Thread 2"] --> YoungGeneration["Young Generation"]

ApplicationThreads["Application Threads"] --> GcThreadN["GC Thread N"]

GcThreadN["GC Thread N"] --> OldGeneration["Old Generation"]

YoungGeneration["Young Generation"] --> ApplicationResumes["Application Resumes"]

Characteristics of Parallel GC

  • Multiple GC threads
  • High throughput
  • Better CPU utilization
  • Longer pause times than low-latency collectors
  • Suitable for batch workloads

Enable Parallel GC

java -XX:+UseParallelGC Application

Serial GC vs Parallel GC

Feature Serial GC Parallel GC
GC Threads One Multiple
CPU Usage Low High
Throughput Lower Higher
Pause Time Longer Shorter than Serial for large heaps
Best For Small Applications Batch Processing
Multi-core Support No Yes

Internal Working of Serial GC

flowchart TD

ObjectAllocation["Object Allocation"] --> EdenMinorGcSurvivor["Eden --> Minor GC --> Survivor Space --> Promotion --> Old Generation --> Full GC"]

Only one GC thread performs all phases.

Internal Working of Parallel GC

flowchart TD

ObjectAllocation["Object Allocation"] --> EdenParallelMinorGc["Eden --> Parallel Minor GC --> Parallel Survivor Processing --> Promotion --> Parallel Old Generation Collection"]

Multiple GC threads process different heap regions simultaneously.

Stop-The-World Events

Both collectors perform Stop-The-World Garbage Collection.

flowchart LR

ApplicationRunning["Application Running"] --> StoptheworldGarbageCollectionApplication["Stop-The-World --> Garbage Collection --> Application Continues"]

Difference:

  • Serial GC → One GC thread
  • Parallel GC → Multiple GC threads

Throughput

Throughput measures how much time the JVM spends executing application code compared to Garbage Collection.

Formula:

Throughput = Application Time
             ---------------------------
             Application Time + GC Time

Higher throughput means more CPU time is spent executing business logic.

Parallel GC is designed to maximize throughput.

Production Example

Suppose a Spring Batch application processes 20 million records overnight.

Requirements:

  • High throughput
  • Long-running batch
  • Pause time is not critical

Recommended Collector:

Parallel GC

Reason:

  • Utilizes multiple CPU cores.
  • Maximizes processing speed.
  • Longer pauses are acceptable because no user is waiting for responses.

Frequently Asked Interview Questions

Question 1

What is Serial Garbage Collector?

Answer

Serial GC is the simplest JVM Garbage Collector.

It uses one GC thread for all collection activities.

During collection:

  • All application threads stop.
  • One GC thread performs Minor or Full GC.
  • Application resumes afterward.

Question 2

When should Serial GC be used?

Answer

Serial GC is suitable for:

  • Small heap sizes
  • Single-core systems
  • Command-line utilities
  • Development environments
  • Embedded applications

It is generally not recommended for high-throughput server applications.

Question 3

What is Parallel Garbage Collector?

Answer

Parallel GC uses multiple Garbage Collection threads to reclaim memory faster.

It is also known as the Throughput Collector because it aims to maximize application throughput.

Question 4

Why is Parallel GC called the Throughput Collector?

Answer

Because its primary goal is to maximize the amount of time spent running application code rather than Garbage Collection.

It sacrifices pause time to achieve higher throughput.

Question 5

What is the main difference between Serial GC and Parallel GC?

Answer

Serial GC Parallel GC
Single GC thread Multiple GC threads
Lower throughput Higher throughput
Suitable for small applications Suitable for large applications
Simpler implementation Better CPU utilization

Question 6

Does Parallel GC eliminate Stop-The-World pauses?

Answer

No.

Parallel GC still pauses all application threads.

The difference is that multiple GC threads perform the collection work simultaneously.

Question 7

Which collector performs better on multi-core processors?

Answer

Parallel GC.

It distributes GC work across multiple CPU cores, significantly reducing collection time compared to Serial GC.

Question 8

Which Garbage Collector is better for batch processing?

Answer

Parallel GC.

Batch applications usually prioritize:

  • Throughput
  • CPU utilization
  • Overall execution time

Pause time is less important.

Question 9

Which Garbage Collector is better for REST APIs?

Answer

Usually not Serial or Parallel GC.

Modern REST APIs generally use:

  • G1GC
  • ZGC
  • Shenandoah

These collectors provide lower pause times.

Question 10

Which JVM option enables Serial GC?

Answer

-XX:+UseSerialGC

Question 11

Which JVM option enables Parallel GC?

Answer

-XX:+UseParallelGC

Question 12

How many GC threads does Parallel GC use?

Answer

The JVM determines the number of GC threads based on:

  • Number of available processors
  • JVM version
  • Heap size

It can also be configured manually.

Example:

-XX:ParallelGCThreads=8

Question 13

Can Parallel GC perform Minor and Full GC?

Answer

Yes.

Parallel GC supports:

  • Minor GC
  • Major GC
  • Full GC

Multiple GC threads participate in these operations.

Question 14

What are the disadvantages of Serial GC?

Answer

  • Long pause times
  • Poor scalability
  • Single-threaded collection
  • Low throughput
  • Unsuitable for large heaps

Question 15

What are the disadvantages of Parallel GC?

Answer

  • Stop-The-World pauses still occur.
  • Pause times increase with larger heaps.
  • Not suitable for latency-sensitive applications.
  • Higher CPU usage during GC.

Question 16

Does Parallel GC always outperform Serial GC?

Answer

No.

For very small applications with small heaps, Serial GC may perform equally well or even slightly better due to lower coordination overhead.

Question 17

How do you identify which Garbage Collector is being used?

Answer

Use:

java -Xlog:gc -version

or

java -XX:+PrintCommandLineFlags -version

The output shows the selected collector.

Question 18

Why isn't Parallel GC the default collector anymore?

Answer

Modern applications prioritize low response times over raw throughput.

G1GC became the default because it offers:

  • Predictable pause times
  • Better large heap support
  • Balanced throughput and latency

Question 19

What causes long GC pauses in Parallel GC?

Answer

Common reasons include:

  • Large heap sizes
  • Large Old Generation
  • Frequent Full GC
  • Memory leaks
  • Excessive object allocation
  • Insufficient heap tuning

Question 20

Which Garbage Collector would you choose for these scenarios?

Scenario Recommended Collector
Small CLI Tool Serial GC
Spring Batch Job Parallel GC
High-Traffic REST API G1GC
Low-Latency Trading System ZGC
Large Heap Microservice G1GC

Real-Time Production Scenario

Problem

A banking application processes 15 million transactions every night.

Characteristics:

  • No interactive users
  • Batch workload
  • High CPU availability
  • Large heap

Current GC:

  • Serial GC

Issues:

  • Long execution time
  • CPU underutilization

Solution

Switch to Parallel GC:

-XX:+UseParallelGC

Result:

  • Multiple GC threads
  • Better CPU utilization
  • Faster batch completion
  • Higher throughput

Best Practices

  • Use Serial GC only for small applications.
  • Use Parallel GC for CPU-intensive batch workloads.
  • Avoid Parallel GC for low-latency REST APIs.
  • Monitor GC logs regularly.
  • Tune heap size before changing collectors.
  • Benchmark under production-like workloads.

Common Mistakes

❌ Assuming Parallel GC eliminates Stop-The-World.

❌ Using Serial GC in large enterprise applications.

❌ Choosing a collector without measuring application behavior.

❌ Ignoring GC logs during performance tuning.

❌ Optimizing GC before fixing memory leaks.

Interview Tips

Senior interviewers commonly ask:

  • Why is Parallel GC called the Throughput Collector?
  • Explain the difference between throughput and latency.
  • Why does Parallel GC still pause application threads?
  • When would you choose Serial GC?
  • Why isn't Parallel GC the default in modern JDKs?
  • How do you tune the number of GC threads?
  • Which collector would you recommend for batch jobs and why?

Strong candidates explain trade-offs rather than claiming one collector is universally better.

Summary

In this article, we covered:

  • Serial Garbage Collector
  • Parallel Garbage Collector
  • Internal architecture
  • Stop-The-World behavior
  • Throughput concepts
  • JVM options
  • Performance comparison
  • Production scenarios
  • Frequently asked interview questions
  • Best practices
  • Common mistakes

In the next article, we'll explore G1 Garbage Collector (G1GC), including regions, concurrent marking, remembered sets, mixed collections, humongous objects, pause-time prediction, and why G1GC became the default collector in modern Java.