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

store stats on scan cache hits and misses #19

Closed
dylanhross opened this issue Aug 25, 2023 · 0 comments
Closed

store stats on scan cache hits and misses #19

dylanhross opened this issue Aug 25, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@dylanhross
Copy link
Collaborator

When scan caching is turned on for the MZA object, whenever scans are accessed increment one of two counters (as instance variables) reflecting whether it was a cache hit or miss. These values can even be stored in the scan cache file itself and keep track over a long term the cache hits/misses. At least as instance variables they could be pretty useful for characterizing performance.

@dylanhross dylanhross added the enhancement New feature or request label Aug 25, 2023
dylanhross pushed a commit that referenced this issue Jan 30, 2024
…les as well as the scan cache itself (address #19). At present these are private instance variables but the data is stored and able to be accessed at least
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant