act
Tendis
act | Tendis | |
---|---|---|
2 | 8 | |
188 | 2,826 | |
0.0% | 0.5% | |
3.9 | 8.2 | |
about 1 month ago | 3 months ago | |
C | C++ | |
GNU General Public License v3.0 or later | 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.
act
-
Probing My SSD's Latency
The Aerospike ACT benchmarking tool characterizes flash devices on their latency under a fixed read/write profile. It won't tell you how fast your device is, it will tell you if a workload runs under a certain latency bound.
https://docs.aerospike.com/server/operations/plan/ssd/ssd_ce...
https://github.com/aerospike/act
If you set
max-lag-sec: 0
-
IceFireDB: Distributed disk storage database based on Raft and Redis protocol
It depends, yes but ... (not discounting any of the above).
One sees a lot of 3:1 in practice due to the replication factor. If you have 3 copies of the data and the client can read from any node, you get 3x the read performance as having to have a quorum write on two out of three nodes.
To the GP, for a rough swag of what is possible out of given hardware, a combination of FIO and ACT (measures IO latency under a fixed load) is a good start.
https://fio.readthedocs.io/en/latest/fio_doc.html
https://github.com/aerospike/act
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
What are some alternatives?
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.
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
fio - Flexible I/O Tester
KeyDB - A Multithreaded Fork of Redis
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
ledisdb - A high performance NoSQL Database Server powered by Go
Seastar - High performance server-side application framework
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.
raids - Cache distribution services: http, websock, redis, memcached
fastonosql_gui - FastoNoSQL is a crossplatform Redis, Memcached, SSDB, LevelDB, RocksDB, UnQLite, LMDB, ForestDB, Pika, Dynomite, KeyDB GUI management tool.