-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal to Integrate SIEVE Eviction Algorithm #173
Comments
I believe this repo is abandoned, We've been maintaining a fork https://github.com/groupcache/groupcache-go with optional S3FIFO |
Tailscale maintain their own fork too, m Edit: Actually it's maintained by someone else at Tailscale, I misremembered! |
Thanks, I didn't know tailscale was maintaining a fork! I maintained a fork at mailgun for years, but now I maintain the implementation at https://github.com/groupcache which is very different from the original library. It no longer uses global variables and has abstracted away the internal cache to allow other implementations to be used. Of interest to me is a lock free cache, which greatly improves performance on high concurrency systems. |
Thank you for sharing this repo! It looks like it uses LRU as the eviction algorithm? |
It has optional support for S3-FIFO https://github.com/groupcache/groupcache-go/blob/main/README.md#otter-cache |
Hi there,
Our team (@1a1a11a) has developed a new cache eviction algorithm, called SIEVE. It’s simple, efficient, and scalable.
Why SIEVE could be a great addition:
Welcome to dive into the details on our website sievecache.com and on our SIEVE blog.
We would love to explore the possibility of integrating SIEVE into groupcache. We believe it could be a beneficial addition to the library and the community.
Looking forward to your feedback!
The text was updated successfully, but these errors were encountered: