Python CPU-Bound vs I/O-Bound Tasks

CPU-bound tasks spend most time calculating, while I/O-bound tasks spend much time waiting for disks, network or user input.

Understanding the Concept

CPU-bound tasks spend most time calculating, while I/O-bound tasks spend much time waiting for disks, network or user input. This distinction guides whether to try processes, threads or asynchronous I/O.

Measure representative workloads; some libraries release the GIL during native CPU work.

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.

from time import perf_counter

def cpu_task():
    return sum(x*x for x in range(10000))

start = perf_counter()
print(cpu_task() > 0)
print(perf_counter() - start >= 0)

Walkthrough: What Each Part Does

• The imports make time available. These are standard-library building blocks unless the example explicitly names an external tool.
• The definition cpu_task creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
• 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

True
True

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

Calling a task I/O-bound merely because it reads one file before a long computation.

Measure representative workloads; some libraries release the GIL during native CPU work.

Practice Exercise

Separate an image pipeline into file-read, resize and file-write stages and classify the costly parts.

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

• Calling a task I/O-bound merely because it reads one file before a long computation.
• Forgetting to handle worker errors and shutdown, even when the normal completion path appears correct.

Key Takeaways

• CPU-bound tasks spend most time calculating, while I/O-bound tasks spend much time waiting for disks, network or user input.
• Measure representative workloads; some libraries release the GIL during native CPU work.
• Practice: Separate an image pipeline into file-read, resize and file-write stages and classify the costly parts.