[KDB-506] read load attribution spike #4649
Draft
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
…ind it on the workitem instead (so that it can vary depending on the user) (not actually setting it in the workitem yet)
timothycoleman
force-pushed
the
timothycoleman/readload-attribution-spike
branch
from
a188b4e to
54ee607
Compare
…o store the tracker in the reader but it makes more sense to do this in the lease
…ll end up in the OS page cache and not the Disk
timothycoleman
changed the title
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.
We capture metrics of #events and #bytes read - this spike breaks these metrics down by user and source (file / chunk cache) to make it easier to see which applications are causing load, and especially disk load.
We also now capture reads for replication