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

Update APM Server throughput number for 8.16.0 #4441

Merged
merged 8 commits into from
Jan 8, 2025
Merged
Prev Previous commit
Next Next commit
resolve reviewer comments
  • Loading branch information
rubvs committed Jan 7, 2025

Verified

This commit was signed with the committer’s verified signature.
pradyunsg Pradyun Gedam
commit ec57fdbcbf734ba2b2ca43cc2355b5012f0635b2
Original file line number Diff line number Diff line change
@@ -7,7 +7,7 @@ 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 _CPU Optimized_ hardware template on AWS, GCP and Azure on {ecloud} with the following instances, for more details see link:https://www.elastic.co/guide/en/cloud/current/ec-configure-deployment-settings.html#ec-hardware-profiles[Hardware Profiles]:
* Using the _CPU Optimized_ hardware template on AWS, GCP and Azure on {ecloud} with the following instances (for more details see link:https://www.elastic.co/guide/en/cloud/current/ec-configure-deployment-settings.html#ec-hardware-profiles[Hardware Profiles]):
rubvs marked this conversation as resolved.
Show resolved Hide resolved
** AWS: c6gd
** Azure: fsv2
** GCP: n2.68x32x45
@@ -32,47 +32,47 @@ specific setup, the size of APM event data, and the exact number of agents.

| *1 GB*
(10 agents)
| 15 180
| 15,180
events/second
| 13 700
| 13,700
events/second
| 17 100
| 17,100
events/second

| *4 GB*
(30 agents)
| 28 890
| 28,890
events/second
| 26 020
| 26,020
events/second
| 34 840
| 34,840
events/second

| *8 GB*
(60 agents)
| 49 660
| 49,660
events/second
| 33 610
| 33,610
events/second
| 47 630
| 47,630
events/second

| *16 GB*
(120 agents)
| 96 120
| 96,120
events/second
| 57 480
| 57,480
events/second
| 90 020
| 90,020
events/second

| *32 GB*
(240 agents)
| 132 800
| 132,800
events/second
| 88 830
| 88,830
events/second
| 143 100
| 143,100
events/second

|====