Concurrency vs Parallelism

They are NOT the same

Dec 01, 2024

Concurrency and parallelism are two of the most misunderstood concepts in system design.

While they might sound similar, they refer to fundamentally different approaches to handling tasks.

Simply put, one is about managing multiple tasks simultaneously, while the other is about executing multiple tasks at the same time.

In this article, we’ll break down the differences between these two concepts, explore how they work, and illustrate their real-world applications with examples and code.

If you’re finding this newsletter valuable and want to deepen your learning, consider becoming a paid subscriber.

As a paid subscriber, you'll receive an exclusive deep-dive article every week, access to a structured System Design Resource (100+ topics and interview questions), and other premium perks.

Unlock Full Access

1. What is Concurrency?

Concurrency means an application is making progress on more than one task at the same time.

In a computer, the tasks are executed using Central Processing Unit (CPU).

While a single CPU can work on only one task at a time, it achieves concurrency by rapidly switching between tasks.

For example, consider playing music while writing code. The CPU alternates between these tasks so quickly that, to the user, it feels like both are happening at the same time.

This seamless switching—enabled by modern CPU designs—creates the illusion of multitasking and gives the appearance of tasks running in parallel.

However, it’s important to note this is not parallel. This is concurrent.

Concurrency is primarily achieved using threads, which are the smallest units of execution within a process. The CPU switches between threads to handle multiple tasks concurrently, ensuring the system remains responsive.

The primary objective of concurrency is to maximize CPU utilization by minimizing idle time.

For example:

When one thread or process is waiting for I/O operations, database transactions, or external program launches, the CPU can allocate resources to another thread.

This ensures the CPU remains productive, even when individual tasks are stalled.

How Does Concurrency Works?

Concurrency in a CPU is achieved through context switching.

Here’s how it works:

Context Saving: When the CPU switches from one task to another, it saves the current task's state (e.g., program counter, registers) in memory.
Context Loading: The CPU then loads the context of the next task and continues executing it.
Rapid Switching: The CPU repeats this process, switching between tasks so quickly that it seems like they are running simultaneously.

The Cost of Context Switching

While context switching enables concurrency, it also introduces overhead:

Every switch requires saving and restoring task states, which consumes both time and resources.
Excessive context switching can degrade performance by increasing CPU overhead.

Real-World Examples of Concurrency

1. Web Browsers

Modern web browsers perform multiple tasks concurrently:

Rendering web pages (HTML/CSS).
Fetching external resources like images and scripts.
Responding to user actions such as clicks and scrolling.

Each of these tasks is managed by separate threads, ensuring the browser remains responsive while loading and displaying content.

2. Web Servers

Web servers like Apache or Nginx handle multiple client requests concurrently:

Each request is processed independently using threads or asynchronous I/O.
For example, a server can handle multiple users loading different pages simultaneously without blocking.

3. Chat Applications

Chat applications perform several operations concurrently:

Processing incoming messages.
Updating the user interface with new messages.
Sending outgoing messages.

This ensures smooth real-time communication without delays or freezes.

4. Video Games

Video games rely heavily on concurrency to deliver an immersive experience:

Rendering graphics.
Processing user input (e.g., character movement).
Simulating physics.
Playing background audio.

For example, while a player moves a character, the game simultaneously updates the environment and plays music, ensuring smooth gameplay.

Code Example

Most popular programming languages come with inbuilt support for creating and managing threads.

Here's an example of a concurrent program in Java:

Output (Interleaved Execution):

Task A - Step 1 Task B - Step 1 Task C - Step 1 Task A - Step 2 Task B - Step 2 Task C - Step 2 ...

Parallelism means multiple tasks are executed simultaneously.

To achieve parallelism, an application divides its tasks into smaller, independent subtasks. These subtasks are distributed across multiple CPUs, CPU cores, GPU cores, or similar processing units, allowing them to be processed in parallel.

To achieve true parallelism, your application must:

Utilize more than one thread.
Ensure each thread is assigned to a separate CPU core or processing unit.

How does Parallelism Works?

Modern CPUs consist of multiple cores. Each core can independently execute a task. Parallelism divides a problem into smaller parts and assigns each part to a separate core for simultaneous processing.

Task Division: The problem is broken into smaller independent sub-tasks.
Task Assignment: Sub-tasks are distributed across multiple CPU cores.
Execution: Each core processes its assigned task simultaneously.
Result Aggregation: Results from all cores are combined to form the final output.

Real-World Examples of Parallelism

1. Machine Learning Training

Training deep learning models involves dividing datasets into smaller batches.
Each batch is processed simultaneously across multiple GPUs or CPU cores, significantly speeding up the training process.

2. Video Rendering

Video frames are rendered independently, making it possible to process multiple frames simultaneously.
For example, rendering a 3D animation becomes much faster when using multiple cores to handle different frames in parallel.

3. Web Crawlers

Web crawlers like Googlebot break a list of URLs into smaller chunks and process them in parallel.
This allows the crawler to fetch data from multiple websites simultaneously, reducing the time to gather information.

4. Data Processing

Big data frameworks like Apache Spark leverage parallelism to handle massive datasets.
Tasks such as analyzing logs from millions of users are distributed across a cluster, enabling simultaneous processing and faster insights.

5. Scientific Simulations

Simulations like weather modeling or molecular interactions require heavy computations.
These computations are divided among multiple cores, allowing simultaneous execution and faster results.

Code Example

Here's a simple example of parallelism in Java using the ForkJoinPool framework to compute the sum of an array in parallel:

Task Splitting: The array is divided into smaller segments until the segment size is below the THRESHOLD.
Parallel Execution: Subtasks are executed in parallel using separate threads from the ForkJoinPool.
Result Combination: Results from all subtasks are combined to compute the final sum.

3. Concurrency and Parallelism Combinations

3.1 Concurrent, Not Parallel

An application can be concurrent without being parallel. In this case:

The application makes progress on multiple tasks at the same time seemingly (concurrently).
However, it achieves this by switching between tasks rapidly, rather than running them simultaneously.
Example: A single-core CPU alternating between tasks, giving the illusion of multitasking.

3.2 Parallel, Not Concurrent

An application can be parallel without being concurrent. Here:

A single task is divided into subtasks, and these subtasks are executed simultaneously on separate cores.
There is no overlap between tasks; one task (and its subtasks) completes before the next task starts.
Example: Video rendering, where a single video is divided into frames, and each frame is processed in parallel.

3.3 Neither Concurrent Nor Parallel

Some applications are neither concurrent nor parallel. This means:

Tasks are executed sequentially, one at a time, without any overlap or parallel execution.
Example: A single-core CPU where only one task is processed, and it completes fully before the next task begins.

3.4 Concurrent and Parallel

An application can be both concurrent and parallel, combining the strengths of both execution models.

In this approach:

Multiple tasks make progress at the same time, and each task is also divided into subtasks that are executed in parallel.
Example: A Multi-core CPU where some subtasks run concurrently on the same core, while others run in parallel on separate cores.

In the above example, a single task is broken into 4 subtasks, which are distributed across 2 CPU cores for parallel execution. These subtasks are executed by multiple threads. Some threads run on the same CPU core (concurrent execution), while others run on separate CPU cores (parallel execution).

If each subtask is executed by its own thread on a dedicated CPU (e.g., 4 threads on 4 CPUs), the task execution becomes fully parallel, with no concurrency involved.

It’s often challenging to break a task into exactly as many subtasks as there are CPUs. Instead, tasks are typically divided into a number of subtasks that align naturally with the problem's structure and number of CPU cores available.

4. Summary

Thank you for reading!

If you found it valuable, hit a like ❤️ and consider subscribing for more such content every week.

If you have any questions or suggestions, leave a comment.

This post is public so feel free to share it.

P.S. If you’re finding this newsletter helpful and want to get even more value, consider becoming a paid subscriber.

As a paid subscriber, you'll receive an exclusive deep dive every week, access to a comprehensive system design learning resource , and other premium perks.

Get full access to AlgoMaster

There are group discounts, gift options, and referral bonuses available.

Checkout my Youtube channel for more in-depth content.

Follow me on LinkedIn, X and Medium to stay updated.

Checkout my GitHub repositories for free interview preparation resources.

I hope you have a lovely day!

See you soon,
Ashish