Release scale testing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
To prepare for the upcoming release, we should do some more involved testing to make sure we've not had any regressions.
## Monitor
Each test should record the following:
- Success rate
- Latency and throughput
- Dashboard load times
- `linkerd stat` responsiveness
- Prometheus cpu/memory usage
## Tests
Each test should be independent.
- 1k services
- 1k pods
- 10k rps for a single pod
Please write up the results and methodology for each of these tests in this issue. Some graphs of the usage from each test would be much appreciated (success, latency, throughput, resource usage).
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 planning independent runs for the three requested scales: 1k services, 1k pods, and 10k requests per second for one pod. Record success, latency, throughput, dashboard load time, `linkerd stat` responsiveness, and Prometheus CPU/memory usage; done means adding methodology, results, and usage graphs for each test to this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, prometheus
- Domain
- observability, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100