3 ms·

When I see that: https://github.com/cirospaciari/socketify.py/blob/main/bench/socketify_plaintext.py#L22 https://github.com/cirospaciari/socketify.py/blob/main/

by Thaxll 4y ago

When I see that: https://github.com/cirospaciari/socketify.py/blob/main/bench/socketify_plaintext.py#L22 https://github.com/cirospaciari/socketify.py/blob/main/bench... It's kind of hopeless, Python still needs to fork per core to get any performance? So if you have 8 cores you're actually running 8 processes, so 8 DB pool etc ...

cirospaciari 4y ago
Python GIL is the problem for multithreading, but I think I have a solution to not need 8 DB pools, soon o will post about it. But yeah it's a waste
- tomwojcik 4y ago
  Oh, I have a pretty fresh news for you. https://github.com/python/peps/pull/2955 https://github.com/python/peps/pull/2955
  - jopython 4y ago
    I wouldn't be excited about PEPs. GIL has been talked about for umpteen years.
  - cirospaciari 4y ago
    WOW that's awesome!
simonw 4y ago
Why does that feel hopeless to you? Running one process per core has been working well for scaling huge websites for decades at this point.
- cirospaciari 4y ago
  nodejs do this and actually Go fiber uses prefork to do this too
  - deleted 4y ago
    [deleted]