AllenInstitute / AllenInstitute/vis
Performance testing and tracking
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- Avg merge
- 10h 24m
- Merged PRs (30d)
- 7
Description
It would be nice to set up some sort of performance testing and tracking over time, so we can be sure to introduce performance regressions over time and identify any bottlenecks that could benefit from being written in a non-GC language.
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
No files, benchmarks, tests, or entry points are named in the issue. Start by defining which visualization workloads need performance coverage and how results should be tracked over time. Done means the scope, regression criteria, and bottleneck-identification process are implemented and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100