[issue42471] Slowdown in socket tests noticed since Py3.8

Change by Ronald Oussoren : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42471] Slowdown in socket tests noticed since Py3.8

Terry J. Reedy added the comment: Should this be closed as 'not a bug'? -- nosy: +terry.reedy ___ Python tracker ___ ___

[issue42471] Slowdown in socket tests noticed since Py3.8

Bert JW Regeer added the comment: Ned: You are correct, I hadn't even considered that as a potential issue. Added a context to grab the fork multiprocessing context and we are back to the speed it was before. This slowdown is pretty huge for just changing the way the process is forked.

[issue42471] Slowdown in socket tests noticed since Py3.8

Ned Deily added the comment: Do your tests use the multiprocessing module? As of 3.8, the default start method for multiprocessing on macOS was changed from “fork” to “spawn”: https://docs.python.org/3.8/library/multiprocessing.html#contexts-and-start-methods -- nosy: +ned.deily,

[issue42471] Slowdown in socket tests noticed since Py3.8

New submission from Bert JW Regeer : I am being fairly vague here, but it is mainly because I don't know the best way to reduce the test cases down to pinpoint the problem. I maintain Waitress, a pure Python HTTP server, and ever since Python 3.8 there's been a marked slowdown of the