xacrimon/dashmap

Blazing fast concurrent HashMap for Rust.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 15 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 16th, 2026
Created on December 6th, 2019
Open Issues & Pull Requests: 74 (+0)
GitHub issues: Enabled
Number of forks: 191
Total Stargazers: 4,115 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.8 days
Mean response time: 110.8 days
90th percentile: 362.3 days
Tracked items: 37

Most active contributors

Sign in to see contributor activity.

How this project is maintained

97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 31
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 692 days
Stale 30+ days: 30
Stale 90+ days: 27

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (2)
  • help wanted (2)
  • p-low (2)
  • wontfix (2)
  • v3 (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

DashMap is a concurrent hash map implementation for Rust that prioritizes performance in multi-threaded environments.

The tool solves the problem of safely sharing and mutating hash map data across threads without the overhead of traditional locking mechanisms. It achieves this through a sharded architecture, where the map is divided into multiple independent segments, each with its own lock. This design reduces contention by allowing different threads to operate on different segments simultaneously, rather than serializing all access through a single lock protecting the entire map.

Developers should choose DashMap when building Rust applications that require frequent concurrent reads and writes to a shared map structure, particularly in scenarios with moderate to high contention. It suits projects where performance is critical and the overhead of synchronization primitives matters. The tool is especially valuable in server applications, caching layers, and data processing pipelines where multiple threads need to access the same collection concurrently.

The project demonstrates consistent maintenance with regular updates addressing performance improvements and bug fixes. Development activity shows responsiveness to user issues and pull requests, indicating active engagement with the community. The codebase receives ongoing refinement to maintain its performance characteristics and reliability in production use.