4 ms·
The Windows kernel scheduler causes much trouble for our simulation software which runs 7 out of 8 cores at full pace, and then mysteriously gets suspended by t
by smallstepforman 7y ago
The Windows kernel scheduler causes much trouble for our simulation software which runs 7 out of 8 cores at full pace, and then mysteriously gets suspended by the kernel when left to run over night. No Microsoft, its not OK to suspend a user task, and it’s not OK to reboot my box for an update while I’m running simulation software. If I end up having to reboot to a non Microsoft OS to run the simulations, I may End up never rebooting back to Win10 (once a solution to our external 3rd party tools is found).
- yummypaint 7y agoThis is triggering some bad memories. I havent used windows for anything serious in almost a decade, but it's pretty mind blowing they still havent fixed their basic reliability and availability issues. It's especially farcical because it flies completely in the face of the marketing claims used to push commercial software over FOSS. I work at a facility where running experiments effectively costs $1000/hour, and we have learned the hard way to not let windows anywhere near anything remotely critical. We dont even use windows to host guis for talking to the back end. About 10 years ago we made a long series of attempts to remedy these problems of windows machines rebooting themselves etc when told not to and losing irreplacable overnight data etc. The only solution that can be trusted long term is total excorcism and switching to an OS that is written to help users compute instead of to make money for MS shareholders. If you absolutely cant use WINE, see if you can run it in a VM to at least mitigate some of the nonsense. Plus you have the option of taking snapshots to hard restore the machine. /rant
- brucedawson 7y agoWhat does the suspension of your tasks look like? I've never seen this happen. Was it a UWP app? I've left calculations running overnight many times on my Windows machine and never had a problem. Was your machine going to sleep based on the power settings? I'll bet that was it.