update benchmark results post-performance audit - #109
Merged
Conversation
memtier_benchmark with 2.4M requests per test (50k/client): - concurrent SET: 4.56M ops/sec (2.3x redis, 6.6x dragonfly) - concurrent GET: 6.62M ops/sec (3.0x redis, 6.5x dragonfly) - p99 latency (P=1): 0.6ms SET, 0.6ms GET redis-benchmark with 1M requests: - concurrent SET: 1.33M ops/sec (1.7x redis) - concurrent GET: 2.00M ops/sec (2.0x redis)
kacy
added a commit
that referenced
this pull request
Feb 19, 2026
memtier_benchmark with 2.4M requests per test (50k/client): - concurrent SET: 4.56M ops/sec (2.3x redis, 6.6x dragonfly) - concurrent GET: 6.62M ops/sec (3.0x redis, 6.5x dragonfly) - p99 latency (P=1): 0.6ms SET, 0.6ms GET redis-benchmark with 1M requests: - concurrent SET: 1.33M ops/sec (1.7x redis) - concurrent GET: 2.00M ops/sec (2.0x redis)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
summary
fresh benchmark run on GCP c2-standard-8 (8 vCPU, us-east1-b) after the performance audit PRs (#106, #107, #108). updates README.md, bench/README.md, and adds raw CSV results.
key results (memtier_benchmark, P=16):
vs dragonfly (memtier, P=16):
P=1 latency (memtier):
what was tested
bench/compare-redis.sh— redis-benchmark, 1M requests, 50 clients, P=16, 8 threadsbench/bench-memtier.sh— memtier_benchmark, 4 threads, 12 clients/thread, 50k req/clientbench/bench-memory.sh— 1M keys, 64B valuesdesign considerations
the concurrent mode ratios improved from ~1.6x to ~2.3-3.0x vs redis after the performance audit changes (thin LTO, pre-computed wire constants, zero-copy string parsing, ahash shard routing). sharded mode shows lower pipelined throughput due to channel routing overhead but matches or exceeds redis at P=1.