Golang-fifo Alternatives

Similar projects and alternatives to golang-fifo

Caffeine

43 15,252 9.7 Java golang-fifo VS Caffeine

A high performance caching library for Java
ristretto

19 5,334 6.1 Go golang-fifo VS ristretto

A high performance memory-bound Go cache
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
xsync

7 906 5.5 Go golang-fifo VS xsync

Concurrent data structures for Go
theine-go

5 218 6.9 Go golang-fifo VS theine-go

high performance in-memory cache
maphash

6 97 3.1 Go golang-fifo VS maphash
otter

1 1,423 8.9 Go golang-fifo VS otter

A high performance lockless cache for Go. (by maypok86)
libCacheSim

2 122 8.3 C golang-fifo VS libCacheSim

a high performance library for building cache simulators
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
sosp23-s3fifo

2 82 6.6 C golang-fifo VS sosp23-s3fifo

The repo for SOSP23 paper: FIFO queues are all you need for cache evictions
go-cache-benchmark

2 2 7.0 Go golang-fifo VS go-cache-benchmark

Cache benchmark for web cache workloads in golang. (by scalalang2)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better golang-fifo alternative or higher similarity.

Suggest an alternative to golang-fifo

golang-fifo reviews and mentions

Posts with mentions or reviews of golang-fifo. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-23.

Otter, Fastest Go in-memory cache based on S3-FIFO algorithm
16 projects | news.ycombinator.com | 23 Dec 2023

Hello, Thank you for replying here :)
Many of answers you replied are reasonable and good.
And I just want to add more comments for others.
1. SIEVE is not scan-resistant, so that, I think it should only be applied for web cache workloads (typlically follows power-law distribution)
2. SIEVE is somewhat scalalbe for read-intensive applications (e.g. blog, shop and etc), because it doesn't require to hold a lock on cahce hit.
3. The purpose of golang-fifo is to provide simple and efficient cache implementation (e.g. hashicorp-lru, groupcache)
4. when increasing contention otter sacrifices 1-2 percent
-> I think that the statement is incorrect. The hit rate varies depending on the total number of objects and the size of the cache, so it should be compared relatively. for example, otter's efficiency decreased by 5% compared to single-threaded when lock contention increased (decreased efficiency makes a mean network latency higher, because it may need to conduct heavy operation e.g. re-calculation, database access and so on)
5. ghost queue : honetly at that time of writing the code, I didn't deep dive into the bucket table implementation, it may not work same as actual bucket hash table (see here: https://github.com/scalalang2/golang-fifo/issues/16)
golang-fifo | Modern cache eviction algorithm implementations.
2 projects | /r/golang | 7 Dec 2023

I'm also implementing cache algorithms, introduced in papers, in golang.you can visit here. Your contribution would be greatly appreciated.