treap alternatives and similar packages
Based on the "Data Structures" category.
Alternatively, view treap alternatives based on common mentions on social networks and blogs.
-
gocache
A complete Go cache library with mutiple stores (memory, memcache, redis, ...), chainable, loadable, metrics cache and more. -
hyperloglog
HyperLogLog implementation with Sparse, LogLog-Beta bias correction and TailCut space reduction. -
Bloomfilter
Face-meltingly fast, thread-safe, marshalable, unionable, probability- and optimal-size-calculating Bloom filter in go -
merkletree
Implementation of a merkle tree providing an efficient and secure verification of the contents of data structures. -
hilbert
Go package for mapping values to and from space-filling curves, such as Hilbert and Peano curves. -
gostl
Data structure and algorithm library for go, designed to provide functions similar to C++ STL. -
remember-go
A universal interface for caching slow database queries (backed by redis, memcached, ristretto, or in-memory). -
count-min-log
A Go implementation Count-Min-Log sketch: Approximately counting with approximate counters (Like Count-Min sketch but using less memory). -
nan
Zero allocation Nullable structures in one library with handy conversion functions, marshallers and unmarshallers.
Get performance insights in less than 4 minutes
Do you think we are missing an alternative of treap or a related project?
Popular Comparisons
README
treap
Package treap implements an immutabe sorted set datastructure using a combination tree/heap or treap.
The algorithms are mostly based on Fast Set Operations Using Treaps
Although the package is oriented towards ordered sets, it is simple to convert it to work as a persistent map. There is a working example showing how to do this.
Benchmark stats
The most interesting benchmark is the performance of insert where a single random key is inserted into a 5k sized map. As the example shows, the treap structure does well here as opposed to a regular immutable map (using full copying). This benchmark does not take into account the fact that the regular maps are not sorted unlike treaps.
The intersection benchmark compares the case where two 10k sets with 5k in common being interesected. The regular map is about 30% faster but this is still respectable showing for treaps.
$ go test --bench=. -benchmem
goos: darwin
goarch: amd64
pkg: github.com/perdata/treap
BenchmarkInsert-4 1000000 2347 ns/op 1719 B/op 36 allocs/op
BenchmarkInsertRegularMap-4 2000 890745 ns/op 336311 B/op 8 allocs/op
BenchmarkIntersection-4 500 3125772 ns/op 1719838 B/op 35836 allocs/op
BenchmarkIntersectionRegularMap-4 500 2436519 ns/op 718142 B/op 123 allocs/op
BenchmarkUnion-4 1000 1451047 ns/op 939846 B/op 19580 allocs/op
BenchmarkDiff-4 500 3280823 ns/op 1742080 B/op 36298 allocs/op
PASS