Implementation of a lock-free dictionary on .Net This fork contain the following changes: - Non-snapshotting Keys and Values properties (Azure Gem) - Attempt at reducing GC pressure (Azure Gem, TODO: Measure effectiveness, seems to be minimal-to-nonexistent-to-imaginary, YMMV) - NonBlockingHashset wrapper (Azure Gem, TODO: Implement a proper one instead of a wrapper) - Capacity getter property (Azure Gem) - Capacity is not doubled on construction (Azure Gem) - Clear with capacity (Azure Gem) - EstimatedCount getter property (Azure Gem) - Removal of the hash mixer (Idea from https://github.com/VSadov/NonBlocking/issues/20#issuecomment-1545057207) - Rename everything from "Concurrent" to "Nonblocking" (Azure Gem) Some changes are specific to my use case. Included types: === NonBlocking.NonBlockingDictionary Lock-free, wait-free implementation of a dictionary. - has the same API as System.Collections.Concurrent.ConcurrentDictionary. - No locks are taken during any operation including Get, Add, Remove, internal resizes etc... - While multiple threads accessing NonBlocking dictionary will help each other in operations such as table resizing, there is no dependency on such behavior. If any thread get unscheduled or delayed for whatever reason, other threads will be able to make progress independently. - NonBlocking dictionary scales linearly with the number of active threads if hardware permits. On most operations NonBlocking dictionary is faster than Concurrent, especially in write-heavy scenarios. Core algorithms are based on NonBlockingHashMap, written and released to the public domain by Dr. Cliff Click. A good overview could be found here: https://www.youtube.com/watch?v=HJ-719EGIts === NonBlocking.NonBlockingHashSet Lock-free, wait-free implementation of a hashset based on NonBlockingDictionary. - No locks are taken during any operation including Get, Add, Remove, internal resizes etc... - While multiple threads accessing NonBlocking dictionary will help each other in operations such as table resizing, there is no dependency on such behavior. If any thread get unscheduled or delayed for whatever reason, other threads will be able to make progress independently. - NonBlocking dictionary scales linearly with the number of active threads if hardware permits. === Counter32 === Counter64 Low-overhead scalable counters. === Disclaimer I, Azure Gem, do not intend to maintain this fork.
FAQs
Implementation of a lock-free dictionary on .Net This fork contain the following changes: - Non-snapshotting Keys and Values properties (Azure Gem) - Attempt at reducing GC pressure (Azure Gem, TODO: Measure effectiveness, seems to be minimal-to-nonexistent-to-imaginary, YMMV) - NonBlockingHashset wrapper (Azure Gem, TODO: Implement a proper one instead of a wrapper) - Capacity getter property (Azure Gem) - Capacity is not doubled on construction (Azure Gem) - Clear with capacity (Azure Gem) - EstimatedCount getter property (Azure Gem) - Removal of the hash mixer (Idea from https://github.com/VSadov/NonBlocking/issues/20#issuecomment-1545057207) - Rename everything from "Concurrent" to "Nonblocking" (Azure Gem) Some changes are specific to my use case. Included types: === NonBlocking.NonBlockingDictionary Lock-free, wait-free implementation of a dictionary. - has the same API as System.Collections.Concurrent.ConcurrentDictionary. - No locks are taken during any operation including Get, Add, Remove, internal resizes etc... - While multiple threads accessing NonBlocking dictionary will help each other in operations such as table resizing, there is no dependency on such behavior. If any thread get unscheduled or delayed for whatever reason, other threads will be able to make progress independently. - NonBlocking dictionary scales linearly with the number of active threads if hardware permits. On most operations NonBlocking dictionary is faster than Concurrent, especially in write-heavy scenarios. Core algorithms are based on NonBlockingHashMap, written and released to the public domain by Dr. Cliff Click. A good overview could be found here: https://www.youtube.com/watch?v=HJ-719EGIts === NonBlocking.NonBlockingHashSet Lock-free, wait-free implementation of a hashset based on NonBlockingDictionary. - No locks are taken during any operation including Get, Add, Remove, internal resizes etc... - While multiple threads accessing NonBlocking dictionary will help each other in operations such as table resizing, there is no dependency on such behavior. If any thread get unscheduled or delayed for whatever reason, other threads will be able to make progress independently. - NonBlocking dictionary scales linearly with the number of active threads if hardware permits. === Counter32 === Counter64 Low-overhead scalable counters. === Disclaimer I, Azure Gem, do not intend to maintain this fork.
We found that ag.nonblocking demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Application Security
/Security News
Socket CEO Feross Aboukhadijeh and a16z partner Joel de la Garza discuss vibe coding, AI-driven software development, and how the rise of LLMs, despite their risks, still points toward a more secure and innovative future.
Research
/Security News
Threat actors hijacked Toptal’s GitHub org, publishing npm packages with malicious payloads that steal tokens and attempt to wipe victim systems.
Research
/Security News
Socket researchers investigate 4 malicious npm and PyPI packages with 56,000+ downloads that install surveillance malware.
