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

missing per-skiplist overheads in MEMORY USAGE #6198

Merged
merged 1 commit into from Jul 10, 2019

Conversation

oranagra
Copy link
Member

@oranagra oranagra commented Jul 4, 2019

these had severe impact for small zsets, for instance ones with just one
element that is longer than 64 (causing it not to be ziplist encoded)

@oranagra
Copy link
Member Author

oranagra commented Jul 4, 2019

p.s. some aspects of MEMORY USAGE use zmalloc_size so they include internal fragmentation, but others do not (like the use of sdsAllocSize instead of sdsZmallocSize).
i think all should include internal fragmentation, since it leads to confusion (people comparing output of MEMORY USAGE with INFO MEMORY)

these had severe impact for small zsets, for instance ones with just one
element that is longer than 64 (causing it not to be ziplist encoded)
@antirez antirez merged commit 7567323 into redis:unstable Jul 10, 2019
@antirez
Copy link
Contributor

antirez commented Jul 10, 2019

@oranagra thanks, merged. Yes it makes sense to include internal fragmentation indeed.

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.

None yet

2 participants