Ability to view and compare profile counters across a run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 34
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 12
Description
Currently the run page shows the difference in "fields" like execution time and code size.
However it would be useful to be able to compare some of the counters from the profiles, like dynamic instruction count etc.
An improvement in a profiling counter isn't necessarily representative of an improvement though, e.g. a higher dynamic instruction count can still have a quicker execution time, so they probably shouldn't be stored in the DB or used to flag regressions. This would just be a "read only" view of some sort for further investigation.
Contributor guide
No contributing guide indexed for this repository
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
The issue points to the run page and profile counters; start by tracing how the run page currently computes and renders field differences, then identify how profile counter data is exposed. Done means a read-only comparison is visible without persisting counters or using them for regression flags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100