Lightning-AI / Lightning-AI/lightning-thunder
[Reporting] Automated bisection to identify significant changes in performance
Open
@kiya00 is already working on this.
Since Feb 24, 2025.
reporting
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
This is an idea that @IvanYashchuk and I had, recording here so we don't forget. fyi @kiya00
Inspired by @kiya00's work on reporting tooling, we think it would be very interesting to have a function that could identify commits that caused significant performance changes. Maybe the function could take an fx graph or reproduction script and a range of dates or commit values and then bisect thunder to identify where performance significantly changed.
We should work out the details of this together.
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.
Assessment
This issue has not been assessed yet.