nscache
theine-go
| nscache | theine-go | |
|---|---|---|
| - | 5 | |
| 10 | 220 | |
| - | - | |
| 7.6 | 6.9 | |
| 8 days ago | 3 months ago | |
| Go | Go | |
| Apache License 2.0 | 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.
nscache
We haven't tracked posts mentioning nscache yet.
Tracking mentions began in Dec 2020.
theine-go
-
Otter, Fastest Go in-memory cache based on S3-FIFO algorithm
In fact, lock-free queues have several problems at once, which prompted me to give up on them almost immediately.
1. Yes, S3-FIFO can be implemented using lock-free queues, but the problem is that each write to a filled cache using this design will cause a large number of additional atomic operations not friendly to the processor's cache, while bp-wrapper on the contrary amortizes this load. And reading with frequency update on hot entries can have a bad effect on performance. In many ways this is exactly what the last posts in my discussion with Ben are about (not really about this, but the current problem with otter read speed is caused by a similar problem). https://github.com/Yiling-J/theine-go/issues/29#issuecomment...
2. But the main problem for me is not even that. Lock-free queues work fine as long as you only need to support Get and Set operations, but as soon as you want to add features to your cache, the complexity of the implementation starts to increase, and some features are very hard to add to such a structure. Also, improving the eviction policy is under a big question mark, because not only do you have to think about how to improve the eviction policy, but also how to avoid locks while doing so or how not to slow down the implementation with your improvements. BP-Wrapper has no such problems at all, allows you to use any eviction policy and focus on improving different parts of your cache independently of each other.
-
rueidis v1, a redis client with client-side caching, has been released under redis org
CacheStore is an interface so I can use a different local cache instead? For example my adaptive cache package Theine, I think the hit ratio will be much higer than the default LRU one.
-
Theine 0.2.0 released. A generic cache which has adaptive hit ratio optimization and proactive ttl expiration
0.2.0 add removal callback and loading cache(with thundering herd protection), take a look: https://github.com/Yiling-J/theine-go
-
Theine - High performance in-memory cache
Theine: https://github.com/Yiling-J/theine-go
What are some alternatives?
imcache - A zero-dependency generic in-memory cache Go library