4 ms·
Oh come on! How can you say that? Of course there's a cost on multiprocess arquitecture, but it doesn't suck at all! Ok, you shouldn't just spawn new processes
by gaelow 12y ago
Oh come on! How can you say that? Of course there's a cost on multiprocess arquitecture, but it doesn't suck at all! Ok, you shouldn't just spawn new processes whenever you need more tasks running concurrently, but how could a modern OS exist without multiprocessing? What would you have us do, go back to MS-DOS? :-)
- zobzu 12y agoIf you read his article - mainly message passing and consequent context switching. Most programs with protected memory - thats anything after windows ME in the windows world, incl. win 98, 95 for example (ie not just ms dos) - don't need too much message passing. Stuff like webservers do (hence the perf advantage of nginx over apache, until they brought mod_event). Heck even web browsers do quite a bit despite his point - they do what they can to send as few messages as possible to compensate.
- gaelow 12y agoYeah, actually I agree with everything on the article but the title. The article does too :-)