dynomite
raids
Our great sponsors
dynomite | raids | |
---|---|---|
3 | 2 | |
4,161 | 4 | |
0.2% | - | |
0.0 | 6.1 | |
11 months ago | 16 days ago | |
C | C++ | |
Apache License 2.0 | 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.
dynomite
-
Copy Redis Data to New Server
https://github.com/Netflix/dynomite - replication and routing
- I deleted 78% of my Redis container and it still works
-
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.
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?
KeyDB - A Multithreaded Fork of Redis
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
redis - Native port of Redis for Windows. Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs. This repository contains unofficial port of Redis to Windows.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.
edis - An Erlang implementation of Redis