3 ms·
You may be right that a lot of software has some CPU bounds parts but I would argue that most code is IO bound. Usually there is a only a small kernel in a pro
by jcoffland 11y ago
You may be right that a lot of software has some CPU bounds parts but I would argue that most code is IO bound. Usually there is a only a small kernel in a program that actually does heavy computation and this is the only place you should use threading.
- Coding_Cat 11y agoWhat's wrong with threading on IO? For example if you have a webserver which has to wait on replies from various other resources while serving enough clients to saturate itself. Sure, performance wise it is probably better to have a fixed number of threads which do their own scheduling in userspace but this requires much more work then a simple if(!finished()){yield();} and making a thread per client.
- jacques_chester 11y ago> What's wrong with threading on IO? To modify JWZ's famous joke: You have a problem. You say, "I know, I'll use threads!" Nowyou prob h2ave lems
- mystikal 11y agohaha, also: Now y