Support Synchronization Dependency with Holistic Trace Analysis #57
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.
Summary
This PR is to process synchronization dependency between the Chakra nodes.
In order to do that, we use CriticalPathAnalyzer in Holistic Trace Analysis (https://github.com/facebookresearch/HolisticTraceAnalysis/blob/main/hta/analyzers/critical_path_analysis.py).
Please note that,
Test Plan
Download and Install HTA (Later version than 5c7898abbc52a1d4051ef6c93365477feb6c08a8 causes error. WIP).
Run trace_link and chakra converter with Resnet-50
Run trace_link and chakra converter with Llama2
Here are traces that I used.
Resnet-50.zip
llama2.zip
Test Result on ASTRA-Sim
Test result shows that supporting Synchonization dependency with those traces does not change the result in ASTRA-Sim.
There might be few reasons, i) Chakra converter already has very strict dependency. ii) There are few Synchronization dependencies. iii) Dependencies within in the same GPU group (in trace_link) are not included to avoid circular dependency, since they share the same PyTorch node ID.
Resnet-50
Llama2