Limited amount of runtime information associated with compiled frames
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- observability, performance
Research direction
No files, tests, or entry points are identified in the issue, so begin by locating where tlparse collects compiled-frame metrics. The work is complete when compiled frames report hit counts and runtime timings, including behavior across multiple recompilations.
Written by the indexing model from the issue text.
Description
tlparse currently is a compile time only metrics collector. However, there is a small amount of runtime information that I think would be really useful:
- How many times a particular compiled frame was hit. In particular, if we recompile multiple times, we might be interested to know how hot each of the particular recompiles are, which tells you if there is some warmup / unspec thing going on, or if there is legitimate multiple dispatch going on
- How quickly the compiled frames run, a sort of poor man's profiling, but mostly I just want to see the timings from a compiled products perspective, as opposed to the usual performance trace perspective
- Dominant language
- Rust
- Stars
- 94
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from meta-pytorch/tlparse
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
meta-pytorch/tlparse#162 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
meta-pytorch/tlparse#161 · 5 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
meta-pytorch/tlparse#153 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
meta-pytorch/tlparse#142 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
meta-pytorch/tlparse#141 · 1 comment ·
All issues in meta-pytorch/tlparse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area: cli bug priority: P2 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day