3 ms·
From reading it over the root cause was in a massively-multiprocess application. In general this is the usual problem of "on windows use threads not processes
by Pxtl 4y ago
From reading it over the root cause was in a massively-multiprocess application. In general this is the usual problem of "on windows use threads not processes for ephemeral parallel tasks" right?
- kevingadd 4y agoThere are also just some workloads that will saturate things. If you hit the mmap infrastructure hard enough on Windows you can saturate the kernel and your mouse cursor will stop moving, I managed to do it with a custom key/value store written in C# once I spun up enough threads hitting mapped files at once. I would assume that on win10/11 (this was a while ago) it is harder to saturate a modern machine, though, especially if you lower the i/o priority of your process.