4 ms·
In a forking model that shouldn’t be the case, I guess all the workers are loading and initializing things post-fork that likely could have been accomplished pr
by berkle4455 4y ago
In a forking model that shouldn’t be the case, I guess all the workers are loading and initializing things post-fork that likely could have been accomplished pre-fork?
That said, Python devs are some of the worst engineers I encounter, so it’s not surprising things are being implemented incorrectly.
- wolfgang42 4y agoLast I heard, forking wasn’t a very effective memory-sharing technique on CPython because of the way it does reference counting: if you load things in before you fork, when the children start doing work they update the refcounts on all those pre-loaded objects and scribble all over that memory, forcing most of the pages to be copied anyway. There seems to have been some recent-ish work on improving this, though: https://peps.python.org/pep-0683/#avoiding-copy-on-write https://peps.python.org/pep-0683/#avoiding-copy-on-write