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

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.

Thread beginning with comment 646577
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: 2 questions
by boudewijn on Tue 11th Jul 2017 11:46 UTC in reply to "RE: 2 questions"
boudewijn
Member since:
2006-03-05

Not thread: process. The distinction is important.

Reply Parent Score: 2

RE[3]: 2 questions
by feamatar on Tue 11th Jul 2017 12:57 in reply to "RE[2]: 2 questions"
feamatar Member since:
2014-02-25

That is a good point.

Reply Parent Score: 2