GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - GestaltEngine/SinkingTree: Concurrent Lock-Free Hash-Map

BranchesTags
Open more actions menu

Latest commit

 

History

15 Commits
15 Commits

Folders and files

NameName
Last commit message
Last commit date
headers
headers
 
 
tests
tests
 
 
.gitignore
.gitignore
 
 
CMakeLists.txt
CMakeLists.txt
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
paper.md
paper.md
 
 

Repository files navigation

'Sinking Tree' hash-map

Almost* lock-free implementation of hash-map, free of limitations other lock-free hash maps impose.

Advantages

  • Allows rehashing without blocking lookups or insertions across the entire range of keys
  • Allows any type of key, isn't limited to atomically CAS-able
  • Good performance in concurrent scenarios
  • Single-thread lookups are as fast as std::unordered_map
  • Infinitely extensible
  • Erasures free memory, no tombstones
  • Does not rely on any reserved invalid key value

Limitations

  • As the actual size of the map grows beyond the expected capacity, insertion, lookup and erase time complexity degrades to O(log log n)
  • Currently, there are opportunities for the map to be less memory-hungry if lock-free atomic shared pointers are implemented, albeit it's still ok without them
  • Relies on hazard pointers for safe key deletion - latency is bad in the worst case
  • *Rehashing requires locking and has the same latency problem (this could be solved with each Put doing a smaller part of the rehashing)
  • Extremely reliant on a good hash-function
  • Requires a seeded hash-function in order to be reliable in worst-case scenarios
  • Currently does not have iterators
  • Does not shrink.

How does it work and why is it named like that

See paper.md for details.

About

Concurrent Lock-Free Hash-Map

Resources

Readme
MIT license
Activity

Stars

1 star

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.