Tendis
raids
Our great sponsors
Tendis | raids | |
---|---|---|
8 | 2 | |
2,822 | 4 | |
2.3% | - | |
8.2 | 6.1 | |
3 months ago | 21 days ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
Tendis
- Redis as a Database
- I deleted 78% of my Redis container and it still works
- Redis Cluster Re-Implemented in Rust: Scaling Redis Easily in Kubernetes
- IceFireDB: Distributed disk storage database based on Raft and Redis protocol
-
IceFireDB:Distributed disk storage database based on Raft and Redis protocol.
There is a project called Tendis, the architecture of IceFireDB is different from it, but they are all based on disk storage and resp protocol. Thank you for your attention and contact at any time
-
KeyDB CEO Interview: Getting into YC with a Fork of Redis
Does anyone have any experience with these other Redis clones? I need to write a benchmark on these someday (the outline for the blog post is already written), but have restricted my yak shaving recently:
- https://github.com/Tencent/Tendis
- https://github.com/Netflix/dynomite
On a separate note, is FLASH supposed to be an acronym? I can't tell if they're referring to flash storage (SSD, NVMe) or they're referring to perhaps a special algorithm that uses flash storage +/- some other features, or some altogether proprietary hardware.
- Tendis distributed storage engine, compatible with Redis protocol
- Tendis: A high-performance distributed storage system
raids
-
Extreme HTTP Performance Tuning: 1.2M API req/s on a 4 VCPU EC2 Instance
Great work, thanks!
I'm curious whether disabling the slow kernel network features competes with an tcp bypass stack. I did my own wrk benchmark [0], but I did not try to optimize the kernel stack beyond pinning CPUs and busypoll, because the bypass was about 6 times as fast. I assumed that there is no way the kernel stack could compete with that. This article shows that I may be wrong. I will definitely check out SO_ATTACH_REUSEPORT_CBPF in the future.
[0] https://github.com/raitechnology/raids/#using-wrk-httpd-load...
-
KeyDB CEO Interview: Getting into YC with a Fork of Redis
https://github.com/raitechnology/raids/.
If you go to the landing page of the above, scroll down to the bottom, there is a TCP bypass solution graphed, using Solarflare Open Onload and it is capable of running several times as fast as the Linux Kernel TCP. I didn't test Redis with Open Onload, but I'm pretty sure you'll get a similar results since TCP is a major performance bottleneck in Redis as well.
What are some alternatives?
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
KeyDB - A Multithreaded Fork of Redis
dynomite - A generic dynamo implementation for different k-v storage engines
IceFireDB - @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
edis - An Erlang implementation of Redis
ledisdb - A high performance NoSQL Database Server powered by Go