Reduce overhead in command propagation#15003
Merged
tezc merged 11 commits intoredis:unstablefrom Apr 15, 2026
Merged
Conversation
Collaborator
Author
ShooterIT
reviewed
Apr 9, 2026
Member
ShooterIT
left a comment
There was a problem hiding this comment.
this idea looks good to me, some small comments
ShooterIT
approved these changes
Apr 10, 2026
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Reviewed by Cursor Bugbot for commit 4eeadae. Configure here.
ShooterIT
reviewed
Apr 14, 2026
ShooterIT
reviewed
Apr 14, 2026
ShooterIT
approved these changes
Apr 14, 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
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.

Refactor command propagation code to reduce overhead on master
Currently, the main bottleneck is
feedReplicationBuffer(). It is called for each argument in the command and has bookkeeping overhead on every call (e.g. checking whether to attach replicas to the replication backlog). It is also not inlined by the compiler. These costs become more visible with pipelining and commands with many arguments (e.g. HSET with many fields).Changes:
replBufWriterAppend().replBufWritterAppendBulkLen()that uses shared RESP headers for small values, avoiding formatting overhead.These changes should not introduce any behavioral change.
TODO: In a follow-up PR, explore forwarding the exact command from the client querybuf to avoid re-serialization. Many commands are propagated without modification and can benefit from this.
--
Co-authored-by: Yuan Wang yuan.wang@redis.com