Spot on, this was the original intent of the linked implementation but the PR eventually did not progress and got rejected[0]. However, it might not be off the

Spot on, this was the original intent of the linked implementation but the PR eventually did not progress and got rejected[0]. However, it might not be off the table yet, because scaling per core is dramatically better especially in moderate to write-heavy scenarios which remains the main use case for ConcurrentDictionary. I have been benchmarking it on arm64 lately and it shows different numbers much more favoring non-blocking implementation without any regressions discussed in the PR. [0] https://github.com/dotnet/runtime/pull/50337 https://github.com/dotnet/runtime/pull/50337