Description
Benchmark scenarios
We currently have 4 benchmarks that leverage the new event handler piece in apmbench to load pre-recorded APM Agent events and replay them to a target APM Server. The current benchmarks are split by language agent but that isn't necessarily the best way to benchmark the APM Server. The current generated data has been gathered from the existing opbeans applications, but that is also not necessarily the best type of application to use for our benchmarks.
We should discuss what kind of benchmark scenarios we'd like to include to be run on a daily basis and the purpose they serve.
Benchmark topologies
Additionally, we should look into the benchmark size matrix we'd like to support, for example:
Objectives / Outcomes:
- Max throughput, APM Server performance with high APM Agent number
- Undersized ES, APM Server should not OOM
| APM Server Size |
Elasticsearch size |
Agent # |
Objective / Outcome |
| 1GB x 1 zone |
16GB x 2 zones |
Medium (600) |
1 |
| 8GB x 1 zone |
16GB x 2 zones |
High (2400) |
1 |
| 8GB x 1 zone |
1GB x 2 zones |
High (2400+) |
2 |
| 8GB x 1 zone |
1GB x 2 zones |
High (2400+) |
2 |
Description
Benchmark scenarios
We currently have 4 benchmarks that leverage the new event handler piece in
apmbenchto load pre-recorded APM Agent events and replay them to a target APM Server. The current benchmarks are split by language agent but that isn't necessarily the best way to benchmark the APM Server. The current generated data has been gathered from the existing opbeans applications, but that is also not necessarily the best type of application to use for our benchmarks.We should discuss what kind of benchmark scenarios we'd like to include to be run on a daily basis and the purpose they serve.
Benchmark topologies
Additionally, we should look into the benchmark size matrix we'd like to support, for example:
Objectives / Outcomes: