Python Multiprocessing — Explain Like I'm 5
Many Kitchens, Not One Kitchen
Imagine baking 1,000 cookies.
If one person uses one oven, it takes a long time. If you have four separate kitchens with four ovens, baking can finish much faster.
Multiprocessing in Python is like using many kitchens.
Each process is a separate Python program with its own memory. They can run at the same time on different CPU cores.
from multiprocessing import Pool
def square(x):
return x * x
if __name__ == "__main__":
with Pool(4) as p:
print(p.map(square, [1, 2, 3, 4]))Output:
[1, 4, 9, 16]
Why not only threads?
Threads share one process, and in normal Python they do not run heavy CPU code fully in parallel because of the GIL.
Processes avoid that limit by being truly separate.
Tradeoff
Processes are powerful but heavier:
- more memory
- slower startup than threads
- data sharing needs messages/copies
So use multiprocessing when CPU work is the main bottleneck.
One Thing to Remember
Multiprocessing uses separate Python processes to get real multi-core speedups for CPU-heavy tasks.
See Also
- Python Async Await Async/await helps one Python program juggle many waiting jobs at once, like a chef who keeps multiple pots moving without standing still.
- Python Basics Python is the programming language that reads like plain English — here's why millions of beginners (and experts) choose it first.
- Python Booleans Make Booleans click with one clear analogy you can reuse whenever Python feels confusing.
- Python Break Continue Make Break Continue click with one clear analogy you can reuse whenever Python feels confusing.
- Python Closures See how Python functions can remember private information, even after the outer function has already finished.