4 ms·
For machines today, I would have to agree with the author. But what happens when a single core is no longer sufficient to handle your "simple" processing requir
by falcolas 16y ago
For machines today, I would have to agree with the author. But what happens when a single core is no longer sufficient to handle your "simple" processing requirements in a timely manner?
Time requirements are constantly getting smaller, and computing requirements are getting larger. Serially generating data, even just for web pages, won't work forever (and I'm willing to hazard a guess that for the major players, it doesn't work now).
Multiprocessing, while a great advancement for Python, is not what I would consider lightweight. It's not a problem for the dual- and quad-core computing era, where you have a few number of spawned processes. However, if you go to a 32 or 64 core era, and the ability of multiprocessing to scale will be dramatically affected by the memory and processing overhead required.
We're fine now with the tools we have. However, if these tools do not evolve, we won't be fine in the future.
- srean 16y agoCould'nt agree more. If the point of the article was: for people who want to do the same old thing then they neednt bother about the new(^) changes, then thats almost a tautology. Someone will find a way to do something useful with the new capabilities of commodity CPUs. If I do not want to delve in those bits, it ensures that the person wont be me. ^ Disclaimer: parallelism/concurrency is far from new though.