<antirez>
8 hours ago
- Redis speed is a selling point, but comparative benchmarks are often misleading due to differences in data models, durability, and testing conditions.
- Fair comparisons require identical protocols and client libraries; otherwise, results reflect network stack and kernel rather than database performance.
- A benchmark comparing Redis and AerospikeDB on large EC2 instances (244 GB RAM) is unrealistic; a smaller m3.medium instance shows Redis achieving 32k ops/sec without pipelining.
- Using pipelining (e.g., 32 operations) boosts Redis performance dramatically: 250k ops/sec on a single core, outperforming the benchmark's multi-core result.
- Benchmarking simple GET/SET operations is insufficient; Redis excels at complex operations like ZADD for leaderboards and HyperLogLog for cardinality estimation, achieving 500k ops/sec combined.
- Better performance comparisons should focus on specific use cases, realistic instance types, and the number of instances needed to handle equivalent traffic.