Releases: jitbit/FastCache
Releases · jitbit/FastCache
1.1.0
- Performance! No double lookups in GetOrAdd, faster Enumerator etc.
- Adde NET8 target (also keeping NET6). Migrated Tests, Benchmarks and CI to NET8
- Fixed build warnings (XML comments for all public API)
- Refactor GetOrAdd methods to reduce duplication
- Added "itemEvicted" callback fixes #6 fixes #11
Full Changelog: 1.0.11...1.1.0
1.0.11
What's Changed
- New
GetOrAdd
overload with factory argument that prevents allocations - Small typos by @jodydonetti in #8
New Contributors
- @jodydonetti made their first contribution in #8
Full Changelog: 1.0.10...1.0.11
1.0.10
- Prevent possible thread starvation in ASP.NET apps (use
SemaphoreSlim
andasync
eviction instead of alock
statement) TryRemove
return value now respects TTL
Full Changelog: 1.0.9...1.0.10
1.0.9
- New API
TryRemove
with anout
variable - Less CPU pressure when multiple
FastCache
instances decide to run a background cleanup job
Full Changelog: 1.0.8...1.0.9
1.0.8
- Faster eviction job (35% faster on large caches of 50k+ items, 10% faster on smaller caches)
- New public API
.EvictExpired()
- call to clean up expired items without waiting for the background timer to pick up
Full Changelog: 1.0.7...1.0.8
1.0.7
What's Changed
- Remove closure allocations in two methods by @rogerioyuuki in #4
New Contributors
- @rogerioyuuki made their first contribution in #4
Full Changelog: 1.0.6...1.0.7
1.0.6
What's Changed
- Remove with value matching by @milokout in #2
- Get rid of
lock(this)
- Performance improvement for
ttlValue.IsExpired()
- Added
Clear()
to empty cache
Full Changelog: 1.0.5...1.0.6
1.0.5
1.0.4
Better concurrency and true atomic for "TryAdd" and "AddOrGet". Unit tests.
1.0.2
.NET 6 targeting, use TickCount64 to eliminate int
overflow logic.