scikit-hep / scikit-hep/integration-tests
Establish a baseline version for performance comparisons?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 3
- Avg merge
- 12h 46m
- Merged PRs (30d)
- 1
Description
Given that we have a relatively large userbase now and multiple sites (effectively) deploying the software stack, we should make a checkpoint for the performance of our software stack and use it as a basis for comparison with simple tests.
We can think about expanding this later into regression testing.
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 repository's nightly GitHub workflows and existing integration tests to understand what software-stack checks already run. Define the performance checkpoint and the simple comparison tests it should include; done means the baseline can be recorded and used for later comparisons.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100