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
[Profiler][Memory] Export raw timestamped events in export_memory_timeline_raw #105094
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/105094
Note: Links to docs will display an error until the docs builds have been completed. ✅ 2 Unrelated FailuresAs of commit 7273bbc: BROKEN TRUNK - The following jobs failed but were present on the merge base e1502c0:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D47416544 |
22aa211
to
9fc1d1e
Compare
This pull request was exported from Phabricator. Differential Revision: D47416544 |
…eline_raw (pytorch#105094) Summary: Pull Request resolved: pytorch#105094 Rather than processing the events into a time and sizes plot, dump the actual events as (timestamp, action, num of bytes, category) when output file ends in `raw.json.gz`. This can allow downstream analysis tools to process these events. It also avoids having to control the granularity of the previous json.gz in memory profiler. Test Plan: CI Tests Differential Revision: D47416544 Pulled By: aaronenyeshi fbshipit-source-id: 770fb2dfa10245e17cd90c03e034d44bbf611f71
…eline_raw (pytorch#105094) Summary: Pull Request resolved: pytorch#105094 Rather than processing the events into a time and sizes plot, dump the actual events as (timestamp, action, num of bytes, category) when output file ends in `raw.json.gz`. This can allow downstream analysis tools to process these events. It also avoids having to control the granularity of the previous json.gz in memory profiler. Test Plan: CI Tests Differential Revision: D47416544 Pulled By: aaronenyeshi fbshipit-source-id: f47fcc3ec7071875a89d20867db2ba14c535c9a0
9fc1d1e
to
85dd6b3
Compare
This pull request was exported from Phabricator. Differential Revision: D47416544 |
…eline_raw (pytorch#105094) Summary: Pull Request resolved: pytorch#105094 Rather than processing the events into a time and sizes plot, dump the actual events as (timestamp, action, num of bytes, category) when output file ends in `raw.json.gz`. This can allow downstream analysis tools to process these events. It also avoids having to control the granularity of the previous json.gz in memory profiler. Test Plan: CI Tests Differential Revision: D47416544 Pulled By: aaronenyeshi fbshipit-source-id: 33c68192d56218f78300733c0a7b68e876a395d8
85dd6b3
to
7273bbc
Compare
This pull request was exported from Phabricator. Differential Revision: D47416544 |
@pytorchmergebot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Summary:
Rather than processing the events into a time and sizes plot, dump the actual events as (timestamp, action, num of bytes, category) when output file ends in
raw.json.gz
.This can allow downstream analysis tools to process these events. It also avoids having to control the granularity of the previous json.gz in memory profiler.
Test Plan: CI Tests
Differential Revision: D47416544
Pulled By: aaronenyeshi