This repository has been archived by the owner on Mar 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
43 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
Fri Mar 29 2019 Piotr Balcer <[email protected]> | ||
|
||
* Version 0.8 | ||
This is the first official release of libvmemcache. It's an embeddable | ||
and lightweight in-memory caching solution designed to fully take | ||
advantage of large capacity memory, such as Persistent Memory with DAX, | ||
through memory mapping in an efficient and scalable way. | ||
|
||
Among other things, it includes: | ||
- Extent-based memory allocator which sidesteps the fragmentation | ||
problem that affects most in-memory databases and allows the cache | ||
to achieve very high space utilization for most workloads. | ||
- Buffered LRU, which combines a traditional LRU doubly-linked | ||
list with a non-blocking ring buffer to deliver high degree | ||
of scalability on modern multi-core CPUs. | ||
- Unique indexing structure, critnib, which delivers | ||
high-performance while being very space efficient. | ||
|
||
The reason this release has version 0.8 is because we are still looking | ||
for actual real world feedback before we stabilize the APIs and commit | ||
to maintaining backward compatibility. It does not mean that the library | ||
is unfinished or unstable. On the contrary, the cache is fully | ||
functional and we are confident in its quality. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters