JuliaDiff / JuliaDiff/AbstractDifferentiation.jl
Establish a benchmark for performance regressions/improvements
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 138
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The PRs contributing backends have used a simple benchmark to decide which overloads are needed. I suggest we formalize this to a benchmark we can run to assess performance impact for any backends of any PRs changing the fallback implementations.
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
Review the simple benchmarks previously used by backend-contributing PRs and determine how they can be formalized for fallback implementations. Done means a repeatable benchmark can assess performance impact for changes affecting any backend, with results suitable for comparing regressions and improvements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100