Interval between highest level CPU op not captured correctly
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 196
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
In the Kineto trace, the gaps between highest level CPU ops is visible. This gap is not captured at the generated Chakra trace. It could lead to problems in ET Replay.
Expected Behavior
Somehow capture this gap properly. Is this to be solved in Chakra? In the downstream tools? That part is still a question.
Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Kineto trace with the generated Chakra trace around the gaps between highest-level CPU operations. Trace where those intervals are generated and determine whether the correction belongs in Chakra or downstream tools such as ET Replay. Done means the gap is captured correctly and ET Replay no longer loses it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100