Calculate Idle Time for All KeyTypes and Display Statistics #64
Conversation
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
…ime in Key statistics tables
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.
Description:
This pull request introduces a new feature to the Redis Memory Analyzer, which calculates the idle time for all key types and displays the minimum, maximum, and mean idle times in the Key Statistics tables. This feature aims to help users better understand key usage patterns and make informed decisions when managing their Redis instances.
Use Case:
In certain projects, a single microservice may consume a large amount of memory in Redis by creating numerous keys. In such cases, users may choose to separate that microservice's Redis instance to better manage memory consumption. This feature will allow users to easily identify and clear keys associated with the microservice in the original Redis instance, freeing up memory.
By utilizing the idle time property, users can determine the key patterns that have not been accessed for an extended period of time. This information can then be used to decide which keys were used by the microservice in question and can be safely removed.
Changes:
Added functionality to calculate idle time for all key types
Updated the Key Statistics tables to display min, max, and mean idle times