4 ms·

Performance comparisons are made against go sync.Map, with cmapv2 on par or sometimes exceeding is on different workloads. It is both lock-free and thread safe,

Performance comparisons are made against go sync.Map, with cmapv2 on par or sometimes exceeding is on different workloads. It is both lock-free and thread safe, using atomic operations. It also supports sharding out of the box. cmapv2 with 10m k/v pairs where keys and values are 64bytes was able to achieve 1.5m w/s and 3m r/s.

pstuart 1y ago
Looks interesting, it would be nice to have the performance comparisons front and center on the readme.
- sirgallo 1y ago
  sounds good, they are a bit hidden right now. also am most likely going to update the other docs.
latchkey 1y ago
I've been using this one for years, can you do comparisons against it? https://github.com/cornelk/hashmap https://github.com/cornelk/hashmap
- jzelinskie 1y ago
  Another good comparison would be against https://pkg.go.dev/github.com/puzpuzpuz/xsync/v3#Map https://pkg.go.dev/github.com/puzpuzpuz/xsync/v3#Map
  - sirgallo 1y ago
    definitely, I can expand my comparisons and benchmarks
    - latchkey 1y ago
      Honestly, if you're better than the rest, I would suggest collaborating with the existing solutions.
- sirgallo 1y ago
  yes I can take a look, thanks for passing that along