Better performance profiling/stress-testing
Open
Nobody has claimed this yet.
feature enhancement
question
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We've just started using k6. Thoughts on how we could make the performance profiling/benchmarking better?
Types of testing?
- Smoke tests
- Load tests
- Stress tests
- Soak tests
Ideas
- https://medium.com/capchase/how-capchase-leverages-profiling-to-improve-performance-in-elixir-ff7f4294a0b1 (thanks @stuartc )
Thresholds: either we change the thresholds to something that's passing, OR our thresholds are failing and in that case we need an issue to improve performance and meet these thresholds.
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 reviewing how the project currently uses k6 and which of the listed smoke, load, stress, or soak tests are in place. Define useful thresholds and profiling goals, then determine whether completion means making the thresholds pass or opening focused performance issues for failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100