[GraphRuntime] Layerwise timing in debug graph runtime #3232
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.
The debug_run in the debug graph runtime runs each layer individually and only once, which is not the best way to get the layerwise timing. The PR replaces debug_run with the more accurate run_individual (implemented in #2569) in the python debug graph runtime.
Before:
After:
Note myadd actually only takes about 0.06 - 0.07 us to run, if you warm the cache up first. In the case of a full model, the right way to get layerwise timing is to let the model run continuously with minimal interruptions for a fixed amount of time, and then take the average to get the runtime of individual layers.
@icemelon9 and @antinucleon please review