WIP: Reader-side Profiling #3778
Merged
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
eisenhauer
force-pushed
the
ReaderProfile
branch
from
26f92dc to
5ae2bab
Compare
pnorbert
approved these changes
Sep 13, 2023
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.
I'm considering this WIP because of things we likely want to discuss. For example, it unconditionally drops profiling JSON in /tmp (with profiled reader file name and PID as part of the JSON filename). Maybe it should do that only when explicitly enabled, maybe the drop location should be configurable, etc. It's only profiling data, metadata and metametadata read times and byte counts. We might add to that other items of interest on the read side.