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.

Permalink for comment 646603
To read all comments associated with this story, please click here.
RE[2]: Apples and oranges
by karunko on Tue 11th Jul 2017 18:58 UTC in reply to "RE: Apples and oranges"
karunko
Member since:
2008-10-28

On old hardware, with less CPU power running an old version of Windows, you would expect the problem to be much worse.
But it was not!
This shows, that it is mainly a problem/bug of newer versions of Windows (after Win7).

No it doesn't. He didn't try Windows 10 on the older hardware so we just don't know what would happen with that particular workload. In other words, both of you are making assumptions and my questions still stand. ;-)


RT.

Reply Parent Score: 2