Cache statistics #52
Open
Cache statistics #52
Conversation
This file contains 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
I implemented some stats for the upper filesystem block usage. For the entire filesystem (Yes! it will consume a lot of memory, 36 bytes per block in this implementation) we now track how many times each block has been read, and how many time it has been written. We also track the "cumulative" time between reads and writes, so in the output we can average them and gather some usage patterns. I added also "collisions" and "replaces" in the hashtable implmementations. TODO: Dump the usage stats (only used blocks just to shorten the output) and the hash collisions stats (better in another FUSE file?)
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.
Branched from 1.4.1 tag.
I implemented some stats for the upper filesystem block usage. For the entire filesystem (Yes! it will consume a lot of memory, 36 bytes per block in this implementation) we now track how many times each block has been read, and how many time it has been written. We also track the "cumulative" time between reads and writes, so in the output we can average them and gather some usage patterns.
I added also "collisions" and "replaces" in the hashtable implmementations.
TODO: Dump the usage stats (only used blocks just to shorten the output) and the hash collisions stats (better in another FUSE file?)