Enable benchmarking / performance profiling
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 14
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
🧹 Tech Debt
Fast uses tachometer and a GitHub action for performance profiling libraries, see example result: https://github.com/microsoft/fast/pull/6113#issuecomment-1160727886
As we move towards developing performance sensitive controls, ie Data Grid, we should have robust benchmarking available to track and avoid regressions in performance as we develop.
Contributor 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.
Research direction
Start by reviewing the Tachometer documentation and the linked tachometer-reporter GitHub Action, then compare them with the example result in microsoft/fast#6113. Define how Nimble's performance-sensitive controls, including Data Grid, should be benchmarked in CI. Done means repeatable benchmarks are available and performance regressions can be tracked during development.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100