clockworklabs / clockworklabs/SpacetimeDB
Tracking issue for iai-callgrind
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
I've forked iai-callgrind (https://github.com/iai-callgrind/iai-callgrind), our repo is https://github.com/clockworklabs/iai-callgrind, there's a few changes made there we could attempt to get that upstreamed. Specifically, we allow customizing which function iai-callgrind is calibrated to look for in order to start recording benchmarking information.
cf #619
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
Start by comparing the clockworklabs/iai-callgrind fork with iai-callgrind upstream, focusing on the customization for the function used to begin recording benchmark information. Review related issue #619 and determine whether that change can be prepared for upstream; done means the desired upstream change is clearly identified and ready to propose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100