linkerd / linkerd/linkerd-examples
additional test dimensions in lifecycle test environment
@siggy is already working on this.
Since Jul 27, 2018.
- Dominant language
- Go
- Stars
- 444
- Forks
- 216
- PR merge metrics
- No merged PRs in 30d
Description
The test environment introduced in BuoyantIO/emojivoto#41, intended to exercising route, telemetry, and service discovery lifecycles in Conduit, includes the following:
- conduit control + data plane
- 1 slow-cooker, 100qps
- 10 HTTP point-to-point servers
- 10 gRPC terminus servers, with container restart every 600 requests (~1 minute)
We should extend this environment to exercise additional dimensions, namely:
- [x] BuoyantIO/emojivoto#45 M number of point-to-point servers
- [x] BuoyantIO/emojivoto#45 N number of terminus servers
- [ ] X call-depth length via point-to-point servers
- [x] BuoyantIO/emojivoto#45 Y discrete call graphs
- [x] BuoyantIO/emojivoto#44 full pod restart, on an interval, rather than container
- [x] BuoyantIO/emojivoto#49 Deployment rolling restart, on an interval
- [x] BuoyantIO/emojivoto#51 injected vs. baseline performance
- [ ] performance at 10qps, 100qps, 1,000qps, 10,000qps
- [x] BuoyantIO/emojivoto#51 with and without TLS (depends on runconduit/conduit#1295)
The `Prometheus Benchmark` Grafana dashboard introduced in https://github.com/runconduit/conduit/pull/984 should provide better performance analysis of Prometheus in Conduit.
Relates to BuoyantIO/emojivoto#42.
---
(this issue copied from BuoyantIO/emojivoto#43)
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.
Assessment
This issue has not been assessed yet.