docs: refresh all benchmarks, remove concurrent mode#275
Merged
Conversation
ran full benchmark suite on GCP c2-standard-8 (8 vCPU): - redis-benchmark: ember 1.9x redis SET, 1.6x GET at P=16 - memtier: competitive with redis across workloads - pipeline scaling: up to 4.2M GET/s at P=256 - encryption: 60% SET overhead at P=16, 0% on reads - gRPC, pub/sub, protobuf, vector sections refreshed - transaction overhead: ~30% for both ember and redis - persistence: ~30% overhead with AOF at high pipeline depths removed all "concurrent mode" references — sharded is now the only execution mode going forward.
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 Intel Xeon @ 3.10GHz), updating every section of bench/README.md except SIFT1M (kept from prior run). all references to "concurrent mode" have been removed — sharded is the only execution mode going forward.
key numbers
redis-benchmark (64B, P=16)
pipeline scaling: 200k → 4.2M GET/s from P=1 to P=256
persistence: ~30% overhead with AOF for both ember and redis at P=16
encryption: 60% SET overhead at P=16, 0% on reads (as expected — encryption only hits AOF writes)
transactions: ~30% overhead for MULTI/SET/EXEC vs bare SET on both systems; ember 1.5x faster than redis
vector similarity: kept from prior run (5.5k insert/s sharded, 1.8k query/s)
what was tested