-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[pytorch profiler] enable iteation tracking for kineto #72292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CI Flow Status⚛️ CI FlowRuleset - Version:
|
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit dad2e5b (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
2b27e50 to
1901e47
Compare
aaronenyeshi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
1901e47 to
34fbed1
Compare
34fbed1 to
6fe32a1
Compare
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
1 similar comment
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
6fe32a1 to
80bfc95
Compare
Summary: Pull Request resolved: pytorch#72292 Integrates the libkineto step() method into pytorch profiler step() invocation. This enables Kineto to track the iteration count and trigger trace collection on iteration boundaries from outside the process. Test Plan: ## Test using pytorch profiler step() method Modified the resnet integration test to use pytorch profiler. Configure it to capture 3 iterations : ``` ACTIVITIES_COMPRESSION_ALGORITHM=GZIP ACTIVITIES_MANIFOLD_PATH=gpu_traces/tree/traces/dynocli/0/1643063194/127.0.0.1/ PROFILE_START_ITERATION=200 ACTIVITIES_WARMUP_ITERATIONS=1 ACTIVITIES_ITERATIONS=3 ``` Run dyno gputrace -gpuconf /tmp/kineto_pytorch.conf The output trace has iterations 202, 203, 204 :) One iteration is skipped due to warmup. (Also its one off due 0 vs 1 indexing) [Trace link](https://www.internalfb.com/intern/perfdoctor/trace_view?filepath=tree%2Ftraces%2Fdynocli%2F0%2F1643063194%2F127.0.0.1%2Flibkineto_activities_501743.json.gz&bucket=gpu_traces) {F695716262} Reviewed By: robieta Differential Revision: D33825241 fbshipit-source-id: e3f7781143370db3c551c82a6d10f5073aac6ebd
|
This pull request was exported from Phabricator. Differential Revision: D33825241 |
80bfc95 to
dad2e5b
Compare
Summary: Pull Request resolved: #72292 Integrates the libkineto step() method into pytorch profiler step() invocation. This enables Kineto to track the iteration count and trigger trace collection on iteration boundaries from outside the process. Test Plan: ## Test using pytorch profiler step() method Modified the resnet integration test to use pytorch profiler. Configure it to capture 3 iterations : ``` ACTIVITIES_COMPRESSION_ALGORITHM=GZIP ACTIVITIES_MANIFOLD_PATH=gpu_traces/tree/traces/dynocli/0/1643063194/127.0.0.1/ PROFILE_START_ITERATION=200 ACTIVITIES_WARMUP_ITERATIONS=1 ACTIVITIES_ITERATIONS=3 ``` Run dyno gputrace -gpuconf /tmp/kineto_pytorch.conf The output trace has iterations 202, 203, 204 :) One iteration is skipped due to warmup. (Also its one off due 0 vs 1 indexing) [Trace link](https://www.internalfb.com/intern/perfdoctor/trace_view?filepath=tree%2Ftraces%2Fdynocli%2F0%2F1643063194%2F127.0.0.1%2Flibkineto_activities_501743.json.gz&bucket=gpu_traces) {F695716262} Reviewed By: robieta Differential Revision: D33825241 fbshipit-source-id: 70983420cf47ebbac7b44bfb6494d314506302c5
|
Hey @briancoutinho. |
Summary: Pull Request resolved: #72292 Integrates the libkineto step() method into pytorch profiler step() invocation. This enables Kineto to track the iteration count and trigger trace collection on iteration boundaries from outside the process. Test Plan: ## Test using pytorch profiler step() method Modified the resnet integration test to use pytorch profiler. Configure it to capture 3 iterations : ``` ACTIVITIES_COMPRESSION_ALGORITHM=GZIP ACTIVITIES_MANIFOLD_PATH=gpu_traces/tree/traces/dynocli/0/1643063194/127.0.0.1/ PROFILE_START_ITERATION=200 ACTIVITIES_WARMUP_ITERATIONS=1 ACTIVITIES_ITERATIONS=3 ``` Run dyno gputrace -gpuconf /tmp/kineto_pytorch.conf The output trace has iterations 202, 203, 204 :) One iteration is skipped due to warmup. (Also its one off due 0 vs 1 indexing) [Trace link](https://www.internalfb.com/intern/perfdoctor/trace_view?filepath=tree%2Ftraces%2Fdynocli%2F0%2F1643063194%2F127.0.0.1%2Flibkineto_activities_501743.json.gz&bucket=gpu_traces) {F695716262} Reviewed By: robieta Differential Revision: D33825241 fbshipit-source-id: 70983420cf47ebbac7b44bfb6494d314506302c5 (cherry picked from commit 96c06ec)
Summary:
Integrates the libkineto step() method into pytorch profiler step() invocation.
This enables Kineto to track the iteration count and trigger trace collection on iteration boundaries from outside the process.
Test Plan:
Test using pytorch profiler step() method
Modified the resnet integration test to use pytorch profiler.
Configure it to capture 3 iterations :
Run
dyno gputrace -gpuconf /tmp/kineto_pytorch.conf
The output trace has iterations 202, 203, 204 :) One iteration is skipped due to warmup. (Also its one off due 0 vs 1 indexing)
Trace link
{F695716262}
Reviewed By: robieta
Differential Revision: D33825241