update benchmark results from gcp c2-standard-8 - #113
Merged
Conversation
kacy
force-pushed
the
update-benchmark-results
branch
from
February 12, 2026 22:58
3399cf6 to
b23fe9f
Compare
kacy
added a commit
that referenced
this pull request
Feb 19, 2026
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
updated benchmark results in README.md and bench/README.md following the sharded mode pipeline throughput optimization (#112). all results from a fresh GCP c2-standard-8 (8 vCPU Intel Xeon @ 3.10GHz), Ubuntu 22.04.
key improvements for sharded mode (redis-benchmark):
what was tested
ran the full benchmark suite on a dedicated GCP VM:
bench/compare-redis.sh— redis-benchmark throughput (ember concurrent, ember sharded, redis, dragonfly)bench/bench-memtier.sh— memtier throughput + latency (all four servers)bench/bench-memory.sh— memory per key comparisondesign considerations
sharded SET throughput under memtier pipelining shows lower numbers than redis-benchmark due to a known interaction between the dispatch-collect pipeline and memtier's connection pattern. GET, mixed workloads, and P=1 are unaffected. redis-benchmark results are more representative for SET-heavy workloads. noted in bench/README.md.