Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.17](backport #4441) Update APM Server throughput number for 8.16.0 #4753

Merged
merged 1 commit into from
Jan 8, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,10 @@ agent and server settings, versions, and protocol.

We tested several scenarios to help you understand how to size the APM Server so that it can keep up with the load that your Elastic APM agents are sending:

* Using the default hardware template on AWS, GCP and Azure on {ecloud}.
* Using the _CPU Optimized_ hardware template on AWS, GCP and Azure on {ecloud} with the following instances (for more details see {cloud}/ec-configure-deployment-settings.html#ec-hardware-profiles[Hardware Profiles]):
** AWS: c6gd
** Azure: fsv2
** GCP: n2.68x32x45
* For each hardware template, testing with several sizes: 1 GB, 4 GB, 8 GB, and 32 GB.
* For each size, using a fixed number of APM agents: 10 agents for 1 GB, 30 agents for 4 GB, 60 agents for 8 GB, and 240 agents for 32 GB.
* In all scenarios, using medium sized events. Events include
Expand All @@ -29,47 +32,47 @@ specific setup, the size of APM event data, and the exact number of agents.

| *1 GB*
(10 agents)
| 9,000
| 15,000
events/second
| 6,000
| 14,000
events/second
| 9,000
| 17,000
events/second

| *4 GB*
(30 agents)
| 25,000
| 29,000
events/second
| 18,000
| 26,000
events/second
| 17,000
| 35,000
events/second

| *8 GB*
(60 agents)
| 40,000
| 50,000
events/second
| 26,000
| 34,000
events/second
| 25,000
| 48,000
events/second

| *16 GB*
(120 agents)
| 72,000
| 96,000
events/second
| 51,000
| 57,000
events/second
| 45,000
| 90,000
events/second

| *32 GB*
(240 agents)
| 135,000
| 133,000
events/second
| 95,000
| 89,000
events/second
| 95,000
| 143,000
events/second

|====
Expand Down
Loading