Papers › A Fast, Minimal Memory, Consistent Hash Algorithm

A Fast, Minimal Memory, Consistent Hash Algorithm

9 Jun 2014arXiv:1406.2294links table onlyarchive 2025-07-28

John Lamping, Eric Veach

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

We present jump consistent hash, a fast, minimal memory, consistent hash algorithm that can be expressed in about 5 lines of code. In comparison to the algorithm of Karger et al., jump consistent hash requires no storage, is faster, and does a better job of evenly dividing the key space among the buckets and of evenly dividing the workload when the number of buckets changes. Its main limitation is that the buckets must be numbered sequentially, which makes it more suitable for data storage applications than for distributed web caching.

PaperPDFCode

Code

14 repositories listed; official and paper-mentioned ones first.

MnO2/jump-consistent-hash mentioned on GitHub report
alextanhongpin/go-jump mentioned on GitHub report
c9s/jchash mentioned on GitHub report
datadog/fliphash-rs mentioned on GitHub report
dynatrace-oss/hash4j mentioned on GitHub report
ericherman/libjumphash mentioned on GitHub report
gsharma/consistent-hash mentioned on GitHub report
jjneely/statsrelay mentioned on GitHub report
ko-han/python-ctools mentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections