You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw that the call stack group was providing stacks out of order. See how index 102534 comes in but it is actually older node
2024-03-14 01:11:14,541 - hta - critical_path_analysis.py:L401 - INFO - ===Exiting node TBackward0, id = 127107.0
2024-03-14 01:11:14,541 - hta - critical_path_analysis.py:L167 - INFO - Adding an edge between nodes 156119 -> 156117 type = CPEdgeType.OPERATOR_KERNEL
2024-03-14 01:11:14,542 - hta - critical_path_analysis.py:L401 - INFO - ==Exiting node autograd::engine::evaluate_function: TBackward0, id = 127106
2024-03-14 01:11:14,542 - hta - critical_path_analysis.py:L167 - INFO - Adding an edge between nodes 156117 -> 156115 type = CPEdgeType.OPERATOR_KERNEL
2024-03-14 01:11:14,542 - hta - critical_path_analysis.py:L370 - INFO - ==Entering node autograd::engine::evaluate_function: TBackward0, id = 102534
2024-03-14 01:11:14,542 - hta - critical_path_analysis.py:L167 - INFO - Adding an edge between nodes 156115 -> 156122 type = CPEdgeType.DEPENDENCY
When we run critical path analysis it errors out due to cycles in the DAG
2024-03-13 01:20:39,328 - hta - critical_path_analysis.py:L867 - ERROR - Critical path algorithm failed due to Graph contains a cycle or graph changed during iteration
This is related to new callstack implementation from #86
When i turned back to older call stack this does not happen, and it passes :)
…#114)
Summary:
This is a quick fix for the issue where were seeing cycles in the critical path
facebookresearch#113
Reviewed By: amoghavs
Differential Revision: D54908634
Summary:
Pull Request resolved: #114
This is a quick fix for the issue where were seeing cycles in the critical path
#113
Reviewed By: amoghavs
Differential Revision: D54908634
fbshipit-source-id: 8cbeffaebbe12ad576c9f4b14df6d5080abe1f5e
🐛 Describe the bug
While doing critical path analysis- that builds a DAG of operations in the trace - I am ending up with cycles in the DAG.
This is how CPA works-
See https://hta.readthedocs.io/en/latest/source/features/lightweight_critical_path_analysis.html#cpu-operator-nesting-and-dependencies
I saw that the call stack group was providing stacks out of order. See how index 102534 comes in but it is actually older node
When we run critical path analysis it errors out due to cycles in the DAG
This is related to new callstack implementation from
#86
When i turned back to older call stack this does not happen, and it passes :)
For more context T182236796
Steps to reproduce
Download trace
We can run this script
Expected behavior
Critical path analysis should pass.
For timebeing I am working around this by using older call stack implmentation.
Environment
OS Mac
Python 3.18
HTA version 4222b7b
Additional Info
No response
The text was updated successfully, but these errors were encountered: