libCacheSim
xsync
libCacheSim | xsync | |
---|---|---|
2 | 7 | |
123 | 917 | |
- | - | |
8.3 | 5.5 | |
29 days ago | about 2 months ago | |
C | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libCacheSim
-
Sieve is simpler than LRU
https://github.com/1a1a11a/libCacheSim/blob/develop/libCache...
-
Otter, Fastest Go in-memory cache based on S3-FIFO algorithm
/u/someplaceguy,
Those LIRS traces, along with many others, available at this page [1]. I did a cursory review using their traces using Caffeine's and the author's simulators to avoid bias or a mistaken implementation. In their target workloads Caffeine was on par or better [2]. I have not seen anything novel in this or their previous works and find their claims to be easily disproven, so I have not implement this policy in Caffeine simulator yet.
[1]: https://github.com/ben-manes/caffeine/wiki/Simulator
[2]: https://github.com/1a1a11a/libCacheSim/discussions/20
xsync
-
Otter, Fastest Go in-memory cache based on S3-FIFO algorithm
The issue is Go stdlib does not have parallel hash map.
We have https://github.com/puzpuzpuz/xsync#map a different Cache line hashmap impl.
- Are there any actively maintained or official Golang libraries for managing work queues?
-
Thread-Local State in Go, Huh?
I've created a pull request to decrease the memory footprint and get rid of the unlucky distribution problem. Goroutines (think, threads) now self-organize: they detect contention via a failed CAS and change the stripe. Going to update the article accordingly to avoid confusion.
-
So long, sync.Map
Could you check the method godoc and the example in this draft PR? I'm going to finalize the PR this weekend and it would be great to hear your opinion.
- puzpuzpuz/xsync: Concurrent data structures for Go. An extension for the standard sync package.
What are some alternatives?
Caffeine - A high performance caching library for Java
taskq - Golang asynchronous task/job queue with Redis, SQS, IronMQ, and in-memory backends
maphash
Tasqueue - A simple, customisable distributed job/worker in Go
sosp23-s3fifo - The repo for SOSP23 paper: FIFO queues are all you need for cache evictions
Faktory - Language-agnostic persistent background job server
golang-fifo - Modern efficient cache design with simple FIFO queue only in Golang
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
otter - A high performance lockless cache for Go.
go - The Go programming language
go-cache-benchmark - Cache benchmark for web cache workloads in golang.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.