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 646573
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: 2 questions
by feamatar on Tue 11th Jul 2017 10:19 UTC in reply to "RE: 2 questions"
feamatar
Member since:
2014-02-25

1. Don't need to be a douche.
2. Fibre is not part of Java, that is part of Windows API.
3. The point of a threadpool is not to create threads.
4. You don't have kernel locks in user mode.
5. If terms used(such as "douche") confuse you, i can try to explain it in simpler english if you like.

Reply Parent Score: 5

RE[3]: 2 questions
by CATs on Tue 11th Jul 2017 12:22 in reply to "RE[2]: 2 questions"
CATs Member since:
2017-06-09

1. Don't need to be a douche.
5. If terms used(such as "douche") confuse you, i can try to explain it in simpler English if you like.

I'm sorry, but words "JAVA programmer" universally have such a horrible reputation that it's only understandable for people to automatically assume there's a very good chance a person is a douche. I understand there are exceptions, though.

Edited 2017-07-11 12:23 UTC

Reply Parent Score: 0