Consideration for cache-efficient skip list
Open
question
up-for-grabs
- Dominant language
- C++
- Stars
- 32.1k
- Forks
- 6.9k
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
I'm wondering if there is consideration to see if the skiplist implementation in RocksDB is cache-efficient, and whether to introduce a cache-efficient version of skiplist?
Some of the research is done to address the issue and introduces some version of cache-efficient skip list:
https://adms-conf.org/2016/sprenger_adms16.pdf
https://par.nsf.gov/servlets/purl/10027800
Contributor guide
Assessment
This issue has not been assessed yet.