Listen to the story of professional programmer Bruce Dawson about his “painful experience” with Windows 10.
New technology is not always better, especially for specific jobs. Recently, Bruce Dawson, a programmer working at Google, shared a computer experience that hung to a point where it was impossible to move the mouse. It is worth mentioning, it is his work machine using 24-core CPU running Windows 10 operating system.
To start the story, Dawson began to see “abnormal signs” on his beloved PC with state-of-the-art configuration. Specifically, his machine uses 24 cores, 48 threads (he avoided mentioning CPU names), SSDs, 64 GB of RAM. While the problem occurred, in his opinion, the CPU was still 50% in idle state, the amount of free RAM was also above this number, and the SSD was almost unrelated in the state he mentioned.
Crashes are hard to accept for people who use high-end PCs for specific tasks such as Dawson. Upon discovering the problem, using very basic skills as a programmer, he used the Event Tracker to identify hangouts. Finally, in the midst of a lot of different light-to-heavy suspensions, he chooses to hang up Task Manager for 1.125 seconds.
The more unusual appearance, when he realized at the time of the hang, his CPU is almost operating at less than 50%, while the crashes are “true” CPU is always at 80 -100%.
After the process of digging up event logs on the computer with special tools (which we did not mention in the article), Dawson realized that the hangover originated in the time Windows 10 points off the running processes. He carefully checked on a weaker CPU with 4 cores, 8 threads also using Windows 10 and met the same situation. The test software he wrote himself, with the ability to create 1,000 processes as quickly as possible and then shut them down, created a crash just like he did on his machine.
It turns out that during shutting down processes, there is a small stage that Windows executes sequentially in a single thread, rather than parallel execution in multiple threads. When there are too many processes to queue up, resulting in crashes.
This problem also happens even when he carefully tried after reboot. Dawson also ran tests on a much lower-powered older machine, using the Intel Core 2 Q8200 CPU from 2008, but running Windows 7. The results surprised him: even though the process was slower, Processes turn off processes as fast as Dawson’s 24-core CPUs, and more importantly, they are executed in parallel. Seems like this “serial procedure” was “invented” along with Windows 10.
This pushed Dawson to the ironic situation: CPU 48 threads, 47 of which “rest” while the machine hangs. Not only that, this greatly influenced Dawson’s actual work: building applications on the machine. As he shared: “I use a 24-core CPU, but still can not move my mouse.” Then imagine the trouble he encountered while working would be uncomfortable, with a series of tasks are launched and off during the build.
At present, this issue has been reported to Dawson by Microsoft. Microsoft said it is investigating, research to overcome. With Dawson, he only said: “Windows 7 is now becoming more attractive.” Hopefully Microsoft fixes this issue early on in Windows 10, otherwise, maybe developers using high-end multi-core CPUs such as Dawson will probably switch back to using Windows 7.