Add support for using Redis MONITOR inputs files as the commands replayed during memtier execution #330
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.
This PR introduces first-class support for driving
memtier_benchmarkworkloads from RedisMONITORoutput files.It adds:
--monitor-input=FILEto load commands captured viaredis-cli MONITOR--monitor-pattern={S|R}to control runtime command selection (Sequential by default, or Random)__monitor_c*__placeholder family for--command:__monitor_c1__,__monitor_c2__, … to replay a specific command from the monitor file__monitor_c@__to select commands at runtime (sequential or random)This enables replaying real traffic and mixing captured workloads with synthetic commands using
--command-ratio, while remaining compatible with both standalone and Redis Cluster deployments.User-facing behavior
Replay a specific captured command on every request:
Runtime-selected replay (sequential by default, random with --monitor-pattern=R):
Documentation
MONITORoutput usingredis-cliMONITORdocumentation