Our great sponsors
-
Redis
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, Bitmaps.
-
redis-benchmarks-specification
The Redis benchmarks specification describes the cross-language/tools requirements and expectations to foster performance and observability standards around redis related technologies. Members from both industry and academia, including organizations and individuals are encouraged to contribute.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
On the latest example of that issue ( EVAL performance ) we're now at 6.2.6 levels as stated in:
https://github.com/redis/redis/issues/10981#issuecomment-134...
Furthermore, as stated in https://redis.com/blog/improving-redis-performance/, we're proactively improving Redis performance both on 7.0 and 7.2, with some cases reaching more than 5X boost in the achievable ops/sec on client p50 latency. This a work not only from Redis Ltd but multiple partners and even competitors =)
Some examples of the Redis 7.0 and 7.2 development cycle performance improvements:
- Use snprintf once in addReplyDouble. Measured improvement of simple ZADD of about 25%.
- Optimized GEO commands ( GEODIST, GEOSEARCH BYBOX and BYRADIOUS ) leading to up to 5.4x more ops/sec and still drop in latency of up to 6.4X in the p50 latency.
You can check the redis repo PRs that affect performance easily via: https://github.com/redis/redis/pulls?q=is%3Apr+label%3Aactio...
Taking this opportunity to also remind that our goal (Redis Performance Teams) is to make Redis Performance open and free of bias in any manner. Anyone can contribute in https://github.com/redis/redis-benchmarks-specification either by asking for specific use-cases to be benchmarked, sharing how they're using Redis so we can map that to new benchmarks, and as always submitting PRs to redis itself.