[Solved] Handle many API requests in parallel vs async/await [closed]

Question

If you have 100 I/O-bound operations, then the 100 operations as a whole are still I/O-bound.

CPU-bound is reserved for things that take a non-trivial amount of CPU time. Yes, technically incrementing a counter and starting the next I/O operation does execute CPU opcodes, but the loop would not be considered “CPU-bound” because the amount of time spent doing I/O is vastly higher than the amount of time doing CPU work.

Accepted Answer

If you have 100 I/O-bound operations, then the 100 operations as a whole are still I/O-bound.

CPU-bound is reserved for things that take a non-trivial amount of CPU time. Yes, technically incrementing a counter and starting the next I/O operation does execute CPU opcodes, but the loop would not be considered “CPU-bound” because the amount of time spent doing I/O is vastly higher than the amount of time doing CPU work.