3 ms·
Even in those examples, it applies mostly to the subset of users who have very large numbers of very simple requests. The ratio of kernel to userland work is b
by acdha 11y ago
Even in those examples, it applies mostly to the subset of users who have very large numbers of very simple requests.
The ratio of kernel to userland work is bad if you're receiving an entire network request just to increment a word in memory but usually quite tolerable if, say, you're shoveling video files out and most of the time is spent in something like sendfile() or if your small request actually requires a non-trivial amount of computation.
- lmm 11y agoIf you're doing nontrivial computation that absolutely dominates the kernel overhead (almost by definition). But how frequent is that? A huge amount of programming boils down to CRUD and very basic transformations, maybe a little bit of fanning out/in, all of which involve minimal actual compute.