Linked by Thom Holwerda on Mon 10th Jul 2017 18:27 UTC

This story begins, as they so often do, when I noticed that my machine was behaving poorly. My Windows 10 work machine has 24 cores (48 hyper-threads) and they were 50% idle. It has 64 GB of RAM and that was less than half used. It has a fast SSD that was mostly idle. And yet, as I moved the mouse around it kept hitching - sometimes locking up for seconds at a time.

So I did what I always do - I grabbed an ETW trace and analyzed it. The result was the discovery of a serious process-destruction performance bug in Windows 10.

Great story.

Permalink for comment 646552
To read all comments associated with this story, please click here.
RE[2]: just terrible...
by Carewolf on Mon 10th Jul 2017 19:50 UTC in reply to "RE: just terrible..."
Member since:

It is not chrome it is the chrome build system, that by default launches a process per virtual core, and doesn't care about load. Though it wouldn't be a problem if W10 didn't have this performance issue on process teardown.

Reply Parent Score: 2