> Suggestions: Well, I don’t know the kernel internals, so I might be way off base, but here are some ideas: ...

5. Don't use Windows, especially on cloud server nodes?

Seriously, we have known this for decades. Use Windows where you are forced to by your IT department.

I develop Windows client software and I need to debug and profile that software, so I need to work on Windows. And, the development tools on Windows are excellent so I'm happy to do that. So, I want bugs like this fixed.

Also, Linux necessarily has a different set of quirks/bugs/issues so "move off this platform because of this issue" is often not worthwhile

What a dive. It would be so nice to have more talented people like Bruce working on free software too :) (yeah, I know, evilcorps do pay)

Correctness bugs are just one type of bug. Performance bugs are another type.

The designation of what should be counted as a bug is less clear for performance bugs but if some operation is slower than it could/should be, and if this slowdown is significant enough to matter, and if fixing the slowdown is quite practical then, yeah, I would definitely call it a bug. I have filed many bug reports for performance issues over the years, and many of them have been addressed.

In the extreme: a computer that runs 0.1% as slow as it's supposed to might as well be crashed.

It is a bug that costs you extra money. Makes extra revenue for Azure, though, so there's that.

Often performance is a feature. In those cases, bad performance is a fault.

I'd say something unintentional is a bug. Perhaps someone can use this in a DoS attack