Re:Python’s Multiprocessing Performance Problem
by mlyle on Thursday March 02, 2023 @04:31PM
(#35002371)
> Note that having a solution setup where the end result is "a ton of small, individual API calls" could possibly indicate a bad system architecture.
Or just a lot of clients with a fair bit of shared state which is best kept resident, which is a pretty common use case.
It's a bummer to write python code that works well, and then gets up to 130% CPU load when you grow your use case... and not have any obvious path to scale upwards despite you having 32 threads of execution around.
Or just a lot of clients with a fair bit of shared state which is best kept resident, which is a pretty common use case.
It's a bummer to write python code that works well, and then gets up to 130% CPU load when you grow your use case... and not have any obvious path to scale upwards despite you having 32 threads of execution around.