Skip to content

Include internal sds fragmentation in MEMORY reporting#7864

Merged
oranagra merged 1 commit intoredis:unstablefrom
oranagra:mem_report_accurate
Oct 1, 2020
Merged

Include internal sds fragmentation in MEMORY reporting#7864
oranagra merged 1 commit intoredis:unstablefrom
oranagra:mem_report_accurate

Conversation

@oranagra
Copy link
Member

The MEMORY command is used for debugging memory usage, so it should include internal
fragmentation, same as used_memory

This PR is a portion of #5159

@oranagra oranagra merged commit eb6241a into redis:unstable Oct 1, 2020
@oranagra oranagra deleted the mem_report_accurate branch October 1, 2020 08:30
oranagra added a commit that referenced this pull request Oct 27, 2020
The MEMORY command is used for debugging memory usage, so it should include internal
fragmentation, same as used_memory

(cherry picked from commit eb6241a)
JackieXie168 pushed a commit to JackieXie168/redis that referenced this pull request Nov 4, 2020
The MEMORY command is used for debugging memory usage, so it should include internal
fragmentation, same as used_memory
jschmieg pushed a commit to memKeyDB/memKeyDB that referenced this pull request Nov 6, 2020
The MEMORY command is used for debugging memory usage, so it should include internal
fragmentation, same as used_memory

(cherry picked from commit eb6241a)
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.

2 participants