5 ms·
This is from 2018. It was extensively discussed at the time. The broad consensus was that it was the .NET runtime's spin implementation at fault, both because
by ajross 6y ago
This is from 2018. It was extensively discussed at the time.
The broad consensus was that it was the .NET runtime's spin implementation at fault, both because of the suboptimal use of the PAUSE instruction itself and because of the overall design that had excessive spinning in a few spots. Effectively, IIRC, they were putting the "pause" instruction on the hot path where they needed to exit the loop synchronously, and that's just wrong. Basically no one sane would look at a change log that said "exit latency from pause will now be similar to a pipeline stall" and done anything but shrug.
It's since been addressed in .NET, as far as I know. And I'm not aware of any other affected code.
- dang 6y agoDiscussion from then: https://news.ycombinator.com/item?id=17336853 https://news.ycombinator.com/item?id=17336853
- dvxvd 6y agoSo.. since 2018.. it was 2.5 years ago.. and nothing changed? Obviously, who cares about ex-customers.. fresh one are generating bigger bonuses...
- IAmEveryone 6y agoWow do I hate this sort of shallow cynicism... Let me guess: companies are always screwing the customer, politicians are all corrupt, the media is always lying, etc.? At least verify the testable facts you're relying before assuming bad faith! The only redeeming quality of your inane comment is how neatly it proves my point.
- ooobit2 6y agoDon't ever, ever, ever, ever... NEVER go to Reddit. I'm losing more neurons than I am patience these days.
- tecleandor 6y agoIt was fixed. https://github.com/dotnet/runtime/issues/8744 https://github.com/dotnet/runtime/issues/8744
- m0xte 6y agoNot completely. I've seen hard deadlocks on ReaderWriterLockSlim on high thread counts on 8+ core nodes on .Net core (2.1). Literally all threads in a process jammed on spin waits. This is especially frustrating as the concurrent collections sit on top of that steaming pile of crap. I've learned to walk in the opposite direction of .Net now.
- m0xte 6y agoReplying to self as I can't edit this now. Whenever I am critical of the .Net framework or CLR there is a flurry of downvotes suddenly. Goes from 2 to -1. It's almost as if there's someone at MSFT saying "look at this shit" to their colleagues in the office. Sorry but this was a monumental piece of shit that took us out in production numerous times on classic .Net framework/CLR and I couldn't even get through to someone who gave a shit despite being a gold partner at the time and raising it on Connect. On Core, standard practice is to work around it because any time you open a ticket it gets autoclosed or ignored or just steamrolled (like the telemetry tickets) I have no choice but to look elsewhere because I know any concerns I raise are ignored. MSFT dug this grave. The company is still the sick old dog it always was. Just a new shiny gown.
- fowl2 6y agoThe change in .Net Core: https://github.com/dotnet/runtime/commit/03bf95c8db9003a5925ca9383dca722a4c651e27 https://github.com/dotnet/runtime/commit/03bf95c8db9003a5925... (The implementation might be different on .Net Framework)