cachegrand
xNVMe
| cachegrand | xNVMe | |
|---|---|---|
| 24 | 3 | |
| 963 | 213 | |
| - | 2.8% | |
| 8.0 | 9.3 | |
| 6 months ago | 2 days ago | |
| C | C | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
cachegrand
-
C++ caching library with tiering (RAM + disc)
Closest that comes to my mind is CacheGrand. It doesn’t have some of the features yet, but I believe @daniele_dll is working on it!
-
[PC][Switzerland] Cheap Rackspace
I use this HW for benchmarking and testing my open source project cachegrand ( https://github.com/danielealbano/cachegrand)
- cachegrand
-
Cachegrand, a fast, Redis compatible, KV store – hashtable documentation
https://github.com/danielealbano/cachegrand/blob/main/docs/a...
When tested with memtier_benchmark, using the Redis protocol, cachegrand itself, on the benchmarking hardware, thanks to the implemented hashtable can reach up to 5 million GET op/s and up to 4.5 million UPSERT op/s without batching, with it up to 60 million GET op/s and up to 26 million UPSERT op/s!
- cachegrand - a blazing fast, Redis compatible, Key-Value store builf for today's hardware - hashtable documentation - capable of delivering up to 112 GET mop/s and 85 UPSERT mop/s on a EPYC 7502P
- Show HN: Cachegrand – a fast OSS Key-Value store built for modern hardware
- Cachegrand – a modern OSS Key-Value store built for today's hardware
xNVMe
- Ask HN: Why are there no open source NVMe-native key value stores in 2023?
-
Anyone using io_uring?
Basically io_uring grew a lot, the latest API offers incredible tools but there are very few examples in any language (xnvme and fio), and in particular I'm struggling to understand how to do it in Rust: where should unsafe code stop? should I simply expose the io_uring api as unsafe, or should I do more work in C and present the ring when ready to rust?
-
libnvme VS xNVMe - a user suggested alternative
2 projects | 4 Mar 2022
The foundation of xNVMe is libxnvme, a user space library for working with NVMe devices. It provides a C API for memory management, that is, for allocating physical / DMA transferable memory when needed. An NVMe command interface allowing you to submit and complete NVMe commands in a synchronous as well as an asynchronous manner. Similar to libnvme, however, with a focus on I/O performance and portability. Thus, xNVMe and the libxnvme library works not just on Linux, but also on FreeBSD, Windows, and MacOS.
What are some alternatives?
dragonfly - A modern replacement for Redis and Memcached
libnvme - C Library for NVM Express on Linux
varnish-cache - Varnish Cache source code repository
VkFFT - Vulkan/CUDA/HIP/OpenCL/Level Zero/Metal Fast Fourier Transform library
examples - Example data structures and algorithms
FEMU - FEMU: Accurate, Scalable and Extensible NVMe SSD Emulator (FAST'18). Please checkout https://github.com/vtess/FEMU for latest developments.
midi-redis - A toy memory store with great performance
openSeaChest - Cross platform utilities useful for performing various operations on SATA, SAS, NVMe, and USB storage devices.
async-std - Async version of the Rust standard library
fio - Flexible I/O Tester
webdis - A Redis HTTP interface with JSON output
KVSSD - KV SSD host software including APIs and drivers