enable post-processing of pre-collected metric events #192
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
…vents from perf are processed 2 times
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.
Enabled to support processing with the --txnrate set to the rate known after collection.
Phase 1 - Collect
Run perfspect metrics with the
rawflag. With this flag, perfspect will produce a metadata file and an events file.Phase 2 - Recreate metrics
Run perfspect metrics with the
input<dir> flag where <dir> is the output directory from Phase 1. Perfspect will generate new metrics files from the metadata and events file.Currently supports only one target's data in the input directory.