Download
To meet the requirements presented at the beginning of this chapter, we implemented our own cache and named it BigCache. The BigCache provides shards, eviction and it omits GC for cache entries. As a result, it is very fast cache even for large number of entries. Freecache is the only one of the available in-memory caches in Go which provides that kind of functionality. BigCache is an alternative solution for it and reduces GC overhead differently, therefore we decided to share it. Fast, concurrent, evicting in-memory cache written to keep big number of entries without impact on performance. BigCache keeps entries on heap but omits GC for them. To achieve that, operations on byte slices take place, therefore entries (de)serialization in front of the cache will be needed in most use cases.
Features
- Requires Go 1.12 or newer
- Use custom initialization because additional memory allocation can be avoided in that way
- Writes and reads in BigCache are faster than in freecache
- BigCache relies on optimization presented in 1.5 version of Go
- Entries are kept in byte slices, to omit GC again
- BigCache does not handle collisions
Project Samples
