2 ms·
> In a world with 400 Gb/s NICs, being IO bound takes some doing. depends on what you call I/O. From the perspective of the caller, that’s the entire stack sta
by Someone 4y ago
> In a world with 400 Gb/s NICs, being IO bound takes some doing.
depends on what you call I/O. From the perspective of the caller, that’s the entire stack starting at a http library call or sql driver call. If those can’t use the hardware to their fullest (or can’t, the way you’re using them) your process becomes I/O bound from its perspective.
- janwas 4y agoFair point :) I'm assuming the stack is doing what it can to avoid being the bottleneck. On a system level, I'd still call what you're describing CPU-bound, as in: unable to use all potential IO capacity.