Re:Unlocking Python's Cores:Energy Implications of Removing ...
by apothegm on Monday March 09, 2026 @09:18AM
(#47308685)
A lot of that has already been solved for by scaling workers to cores along with techniques like greenlets/eventlets that support concurrency without true multithreading to take better advantage of CPU capacity.
[ Parent
| on HN ]
Re:Unlocking Python's Cores:Energy Implications of Removing ...
by kevincox on Monday March 09, 2026 @11:00AM
(#47310004)
But you are still more or less limited to one CPU core per Python process. Yes, you can use that core more effectively, but you still can't scale up very effectively.
Re:Unlocking Python's Cores:Energy Implications of Removing ...
by Sohcahtoa82 on Monday March 09, 2026 @05:15PM
(#47315624)
That's great for concurrency, but doesn't improve parallelism.
Unless you mean you have multiple worker processes (or GIL-free threads).
Re:Unlocking Python's Cores:Energy Implications of Removing ...
by apothegm on Tuesday March 10, 2026 @07:04AM
(#47321619)
Yes, multiple worker processes is what I meant. Few web apps have a meaningful use for parallelism within a single process. So long as you’re keeping all cores busy with independent processes at high concurrency, multithreading adds relatively little.
YMMV if you’re doing a lot of number crunching.