Python Concurrency vs Parallelism: Key Concepts

Concurrency means tasks can make progress during overlapping periods, while parallelism means work runs simultaneously on multiple processing resources.

Understanding the Concept

Concurrency means tasks can make progress during overlapping periods, while parallelism means work runs simultaneously on multiple processing resources. A program can have either or both.

Operating-system scheduling and the interpreter build determine actual simultaneous execution.

How to reason about concurrent execution

Workers may start and finish in a different order on every run. Focus on ownership of data, how work and errors move between workers, and what happens when one worker stops early. Locks protect invariants, queues exchange messages, and explicit shutdown logic prevents blocked or orphaned workers.

Concurrency adds overhead and failure modes. Begin with a working sequential solution, choose bounded worker counts and explicit timeouts, then measure whether overlap or parallel execution improves the target workload.

Worked Example

Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.

import threading
import time

def wait_for_resource(label):
    time.sleep(0.01)
    print(label, "ready")

threads = [threading.Thread(target=wait_for_resource, args=(n,)) for n in ("A", "B")]
for thread in threads: thread.start()
for thread in threads: thread.join()

Walkthrough: What Each Part Does

• The imports make threading, time available. These are standard-library building blocks unless the example explicitly names an external tool.
• The definition wait_for_resource creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
• The loop repeats one well-defined unit of work. Check termination, ordering and whether an item may be processed more than once.
• The coordination call waits for a result or a completion condition. Predict what would happen if the worker failed or never became ready.
• The last lines coordinate completion and inspect results. Actual worker scheduling may differ between executions.

This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.

Example Output

A ready
B ready

The output above was captured by running the example in the available Python environment. The order of concurrent events, durations and platform-dependent values can legitimately differ on your computer.

Important Behavior and Edge Cases

Using the terms concurrent and parallel interchangeably when explaining performance.

Operating-system scheduling and the interpreter build determine actual simultaneous execution.

Practice Exercise

Draw a timeline for two sleeping threads and two CPU workers.

Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.

Further reading: official documentation and API reference.

Common Beginner Mistakes

• Using the terms concurrent and parallel interchangeably when explaining performance.
• Forgetting to handle worker errors and shutdown, even when the normal completion path appears correct.

Key Takeaways

• Concurrency means tasks can make progress during overlapping periods, while parallelism means work runs simultaneously on multiple processing resources.
• Operating-system scheduling and the interpreter build determine actual simultaneous execution.
• Practice: Draw a timeline for two sleeping threads and two CPU workers.