chore: consolidate benchmark scripts and documentation - #54
Merged
Conversation
- move all scripts from scripts/ to bench/ folder - consolidate detailed benchmark results in bench/README.md - simplify main README with high-level comparison table - update Makefile targets to reference new script locations - add sharded mode, dragonfly, and persistence stats to docs
- add ember concurrent mode (--concurrent flag) - keep ember sharded mode (default) - compare both against redis and dragonfly - show ratio comparisons for each pairing
- add --threads flag to redis-benchmark calls (defaults to CPU cores) - multi-threaded benchmark client generates more load - previous results were bottlenecked by single-threaded client
tested on c2-standard-8 with multi-threaded benchmark client: - concurrent: 1.86M SET/sec, 2.49M GET/sec (1.8-2.1x vs redis) - sharded: 864k SET/sec, 966k GET/sec (0.9x vs redis) - vs dragonfly: 3.3-3.8x faster in concurrent mode - memory: 161 bytes/key (redis: 105 bytes/key) - p99 latency: 0.4ms for all modes
kacy
added a commit
that referenced
this pull request
Feb 11, 2026
* chore: consolidate benchmark scripts and documentation - move all scripts from scripts/ to bench/ folder - consolidate detailed benchmark results in bench/README.md - simplify main README with high-level comparison table - update Makefile targets to reference new script locations - add sharded mode, dragonfly, and persistence stats to docs * fix: update benchmark script to test all four modes - add ember concurrent mode (--concurrent flag) - keep ember sharded mode (default) - compare both against redis and dragonfly - show ratio comparisons for each pairing * perf: use multi-threaded redis-benchmark for accurate results - add --threads flag to redis-benchmark calls (defaults to CPU cores) - multi-threaded benchmark client generates more load - previous results were bottlenecked by single-threaded client * docs: update benchmark results with accurate GCP numbers tested on c2-standard-8 with multi-threaded benchmark client: - concurrent: 1.86M SET/sec, 2.49M GET/sec (1.8-2.1x vs redis) - sharded: 864k SET/sec, 966k GET/sec (0.9x vs redis) - vs dragonfly: 3.3-3.8x faster in concurrent mode - memory: 161 bytes/key (redis: 105 bytes/key) - p99 latency: 0.4ms for all modes
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
scripts/intobench/folderbench/README.mdwith comprehensive benchmark results:README.mdbenchmarks section to show high-level comparisonMakefiletargets to reference new script locationswhat was tested
make bench-quick,make bench-compare,make bench-memory,make bench-fullworkcargo test --workspace- all 609 tests passdesign considerations
moved to a two-tier documentation approach:
this keeps the main readme scannable while providing depth for users who want to benchmark themselves.