Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add INFO memory section for squashing replies memory consuming #4147

Merged
merged 2 commits into from
Nov 18, 2024

Conversation

BorysTheDev
Copy link
Contributor

part of the #4002
added INFO memory field "commnads_squashing_replies_bytes" to show the current consumption for replies of squashing commands

@BorysTheDev BorysTheDev force-pushed the add_info_memory_for_squashing_replies branch from f281be5 to 803302e Compare November 18, 2024 16:40
@BorysTheDev BorysTheDev requested a review from romange November 18, 2024 18:06
@BorysTheDev BorysTheDev merged commit e16ef83 into main Nov 18, 2024
12 checks passed
@BorysTheDev BorysTheDev deleted the add_info_memory_for_squashing_replies branch November 18, 2024 19:16
@@ -238,6 +274,7 @@ bool MultiCommandSquasher::ExecuteSquashed(facade::RedisReplyBuilder* rb) {
aborted |= error_abort_ && CapturingReplyBuilder::TryExtractError(replies.back());

CapturingReplyBuilder::Apply(std::move(replies.back()), rb);
current_reply_size_.fetch_sub(Size(replies.back()), std::memory_order_relaxed);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is std::move line above on replies.back()

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That move does nothing there, unfortunately. But I've added a fix https://github.com/dragonflydb/dragonfly/pull/4149/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants