Add performance tests to PR actions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.7k
- Forks
- 772
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 9
Description
It is important to maintain performance parity to std::span (at the very least when Safe Buffers are enabled). In order to track this, we should have performance tests between std::span and gsl::span for the latest standard library implementation across Clang, GCC, and MSVC.
@galenelias put together small benchmark comparing the two implementations on various workloads. They have been attached for convenience and provide a good starting point.
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 examining the attached span_bench.zip benchmarks and the repository's PR actions. Compare std::span and gsl::span across the latest standard library implementations on Clang, GCC, and MSVC; done means the performance tests run in PR actions and provide results for each compiler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- ci-cd, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100