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 646586
To read all comments associated with this story, please click here.
Apples and oranges
by karunko on Tue 11th Jul 2017 12:51 UTC
Member since:

I'm not "a programmer, working for Google, focusing on optimization and reliability" but let me play the devil's advocate and ask:

"What's the point of comparing Windows 10 on a 24 core computer and Windows 7 on an Intel Core 2?"

I mean, how is the comparison meaningful when he's not comparing different version of Windows on the same hardware? How can he put the blame on Windows 10 and not that specific hardware configuration? And why quote Amdahl’s law when only two cores are available in the "good configuration"? To look smart and impress people?

These are honest, non rhetorical and definitely non trolling questions, by the way.


Reply Score: 3