From 12696b4515daaa75c891ab90aeab95e23ee35909 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Thu, 31 Oct 2024 11:36:57 +0200 Subject: [PATCH 01/17] Update the elastic-agent resource consumption docs Signed-off-by: Alexandros Sapranidis --- .../install-elastic-agent.asciidoc | 25 ++++++++++--------- 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 291818cd2..18e73a515 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -1,7 +1,7 @@ [[elastic-agent-installation]] = Install {agent}s -[IMPORTANT] +[IMPORTANT] .Restrictions ==== Note the following restrictions when installing {agent} on your system: @@ -12,7 +12,7 @@ run the commands described here. After the {agent} service is installed and runn make sure you run these commands without prepending them with `./` to avoid invoking the wrong binary. * Running {agent} commands using the Windows PowerShell ISE is not supported. -* See also the <> described on this page. +* See also the <> described on this page. ==== You have a few options for installing and managing an {agent}: @@ -57,9 +57,9 @@ Refer to: * {eck-ref}/k8s-elastic-agent.html[Run {agent} on ECK] -- for {eck} users -- -[IMPORTANT] +[IMPORTANT] .Restrictions in {serverless-short} -==== +==== If you are using {agent} with link:{serverless-docs}[{serverless-full}], note these differences from use with {ess} and self-managed {es}: * The number of {agents} that may be connected to an {serverless-full} project is limited to 10 thousand. @@ -68,21 +68,22 @@ If you are using {agent} with link:{serverless-docs}[{serverless-full}], note th [discrete] [[elastic-agent-installation-minimum-requirements]] -== Minimum requirements +== Resource requirements + +The {agent} resources consumption is influenced by the number of integration and the environment its been running on. + +Using our lab environment as an example, we can observe the following resource consumption: -The following are the minimum system requirements for installing {agent}. // lint ignore mem [discrete] === CPU and RSS memory size -// lint ignore 2vcpu 1gb -Minimum requirements have been determined by running the {agent} on a GCP `e2-micro` instance (2vCPU/1GB). -The {agent} used the default policy, running the system integration and self-monitoring. - +// lint ignore 4 vCPU 16.0 GiB We tested in AWS m7i.xlarge instance type that has 4 vCPUs, 16.0 GiB of memory and up to 12.5 Gibps of bandwidth. Ingesting a single log file, running with the throughput preset with self-monitoring enabled. |=== -| **CPU** | Under 2% total, including all monitoring processes -| **RSS memory size** | 400 MB +| **CPU** | ~40% total, including all monitoring processes +| **RSS memory size** | ~310 MB |=== + Adding integrations will increase the memory used by the agent and its processes. [discrete] From 4e17ab4552b8e11b95fea743f46d6d6237f4d63e Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Thu, 31 Oct 2024 11:51:48 +0200 Subject: [PATCH 02/17] Add network read/write throughput Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 18e73a515..a2565e50f 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -81,7 +81,9 @@ Using our lab environment as an example, we can observe the following resource c // lint ignore 4 vCPU 16.0 GiB We tested in AWS m7i.xlarge instance type that has 4 vCPUs, 16.0 GiB of memory and up to 12.5 Gibps of bandwidth. Ingesting a single log file, running with the throughput preset with self-monitoring enabled. |=== | **CPU** | ~40% total, including all monitoring processes -| **RSS memory size** | ~310 MB +| **RSS memory size** | ~310 MB, including all processes +| **Write network throughput** | ~3.4 MB/s +| **Read network throughput** | ~40 KB/s |=== Adding integrations will increase the memory used by the agent and its processes. From 4b893657f5054ccd13fe4fcf8404ec82697d3766 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Thu, 31 Oct 2024 16:25:27 +0200 Subject: [PATCH 03/17] Fix new line Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index a2565e50f..fa16c3f2f 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -78,7 +78,8 @@ Using our lab environment as an example, we can observe the following resource c [discrete] === CPU and RSS memory size -// lint ignore 4 vCPU 16.0 GiB We tested in AWS m7i.xlarge instance type that has 4 vCPUs, 16.0 GiB of memory and up to 12.5 Gibps of bandwidth. Ingesting a single log file, running with the throughput preset with self-monitoring enabled. +// lint ignore 4 vCPU 16.0 GiB +We tested in AWS m7i.xlarge instance type that has 4 vCPUs, 16.0 GiB of memory and up to 12.5 Gibps of bandwidth. Ingesting a single log file, running with the throughput preset with self-monitoring enabled. |=== | **CPU** | ~40% total, including all monitoring processes | **RSS memory size** | ~310 MB, including all processes From cf7644155b4235aebba0573fe775c43325d4aad9 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Fri, 1 Nov 2024 12:25:44 +0200 Subject: [PATCH 04/17] Rename anchor name Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index fa16c3f2f..c2c5dc5b7 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -12,7 +12,7 @@ run the commands described here. After the {agent} service is installed and runn make sure you run these commands without prepending them with `./` to avoid invoking the wrong binary. * Running {agent} commands using the Windows PowerShell ISE is not supported. -* See also the <> described on this page. +* See also the <> described on this page. ==== You have a few options for installing and managing an {agent}: @@ -67,7 +67,7 @@ If you are using {agent} with link:{serverless-docs}[{serverless-full}], note th ==== [discrete] -[[elastic-agent-installation-minimum-requirements]] +[[elastic-agent-installation-resource-requirements]] == Resource requirements The {agent} resources consumption is influenced by the number of integration and the environment its been running on. From 345f231e7fba531beed206c551c598f3b8af9bcd Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Fri, 1 Nov 2024 15:31:02 +0200 Subject: [PATCH 05/17] Fix link Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index c2c5dc5b7..21d2b607f 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -12,7 +12,7 @@ run the commands described here. After the {agent} service is installed and runn make sure you run these commands without prepending them with `./` to avoid invoking the wrong binary. * Running {agent} commands using the Windows PowerShell ISE is not supported. -* See also the <> described on this page. +* See also the <> described on this page. ==== You have a few options for installing and managing an {agent}: From 571c87d59ae819e299ecd6445611a670d3371796 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Fri, 1 Nov 2024 17:33:24 +0200 Subject: [PATCH 06/17] Lowered the instance type and added the input filesize Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 21d2b607f..9f5f74f6b 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -78,12 +78,12 @@ Using our lab environment as an example, we can observe the following resource c [discrete] === CPU and RSS memory size -// lint ignore 4 vCPU 16.0 GiB -We tested in AWS m7i.xlarge instance type that has 4 vCPUs, 16.0 GiB of memory and up to 12.5 Gibps of bandwidth. Ingesting a single log file, running with the throughput preset with self-monitoring enabled. +// lint ignore 2 vCPU 16.0 GiB +Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 GiB of Ram and up to 12.5 Gibps of bandwidth. We ingested a 1.1GB single apache JSON log file, running with the throughput preset and self-monitoring enabled. |=== -| **CPU** | ~40% total, including all monitoring processes +| **CPU** | ~80% total, including all monitoring processes | **RSS memory size** | ~310 MB, including all processes -| **Write network throughput** | ~3.4 MB/s +| **Write network throughput** | ~3.6 MB/s | **Read network throughput** | ~40 KB/s |=== From e212b5dfe73f35643383d5874c8a279ad1e285a6 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Mon, 4 Nov 2024 15:14:57 +0200 Subject: [PATCH 07/17] Add scale preset to the resource table Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 9f5f74f6b..35340482c 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,14 +79,18 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 GiB of Ram and up to 12.5 Gibps of bandwidth. We ingested a 1.1GB single apache JSON log file, running with the throughput preset and self-monitoring enabled. +Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 GiB of Ram and up to 12.5 Gibps of bandwidth. We ingested a 1.1GB single apache JSON log file, running with the throughput and scale preset and self-monitoring enabled. +[options,header] |=== -| **CPU** | ~80% total, including all monitoring processes -| **RSS memory size** | ~310 MB, including all processes -| **Write network throughput** | ~3.6 MB/s -| **Read network throughput** | ~40 KB/s +|Resource | Throughput | Scale +| **CPU*** | ~80% total | ~20% +| **RSS memory size*** | ~310 MB | ~220 MB +| **Write network throughput** | ~3.6 MB/s | 990 KB/s +| **Read network throughput** | ~40 KB/s | ~2.4 KB/s |=== +* including all monitoring processes + Adding integrations will increase the memory used by the agent and its processes. [discrete] From bc7cb4aa05b4e3a3061c2140ff496c42e528cae3 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Mon, 4 Nov 2024 15:26:23 +0200 Subject: [PATCH 08/17] Adjusted the throughput values with the more recent runs Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 35340482c..6a57920e2 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -83,8 +83,8 @@ Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 G [options,header] |=== |Resource | Throughput | Scale -| **CPU*** | ~80% total | ~20% -| **RSS memory size*** | ~310 MB | ~220 MB +| **CPU*** | ~70% total | ~20% +| **RSS memory size*** | ~280 MB | ~220 MB | **Write network throughput** | ~3.6 MB/s | 990 KB/s | **Read network throughput** | ~40 KB/s | ~2.4 KB/s |=== From 09c0d6fa8c107c63728174361ebdeeaa23024eb1 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Mon, 4 Nov 2024 17:40:04 +0200 Subject: [PATCH 09/17] Update wording Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 6a57920e2..0776c234e 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,7 +79,7 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 GiB of Ram and up to 12.5 Gibps of bandwidth. We ingested a 1.1GB single apache JSON log file, running with the throughput and scale preset and self-monitoring enabled. +We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file, running with the throughput preset with self monitoring enabled. [options,header] |=== |Resource | Throughput | Scale @@ -89,7 +89,7 @@ Out testing was performed on AWS m7i.large instance type that has 2 vCPUs, 8.0 G | **Read network throughput** | ~40 KB/s | ~2.4 KB/s |=== -* including all monitoring processes +\* including all monitoring processes Adding integrations will increase the memory used by the agent and its processes. From 69601ae3e191a82d7f8e2088ffe3e39cc2e2d432 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Tue, 5 Nov 2024 09:49:45 +0200 Subject: [PATCH 10/17] Properly escape the asterisk Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 0776c234e..445e1b7cf 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -89,7 +89,7 @@ We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memor | **Read network throughput** | ~40 KB/s | ~2.4 KB/s |=== -\* including all monitoring processes +^*^ including all monitoring processes Adding integrations will increase the memory used by the agent and its processes. From c1d6592f235e47e106ab2baaa07989603f37a335 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Tue, 5 Nov 2024 09:50:21 +0200 Subject: [PATCH 11/17] Update docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc Co-authored-by: Craig MacKenzie --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 445e1b7cf..26174fd55 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,7 +79,7 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file, running with the throughput preset with self monitoring enabled. +We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the throughput and scale preset with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using [Elastic Defend](https://www.elastic.co/docs/current/integrations/endpoint). [options,header] |=== |Resource | Throughput | Scale From 403920e234cf2d1c2b1636f96620c14da6a74f6b Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Tue, 5 Nov 2024 17:01:05 +0200 Subject: [PATCH 12/17] Update docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 26174fd55..29d8dd38c 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,7 +79,7 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the throughput and scale preset with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using [Elastic Defend](https://www.elastic.co/docs/current/integrations/endpoint). +We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the throughput and scale preset with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header] |=== |Resource | Throughput | Scale From 61b626e18843c1d76b7ff749cff06ca538fc07ec Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Tue, 5 Nov 2024 17:25:02 +0200 Subject: [PATCH 13/17] Add link to the presets Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 29d8dd38c..e47092c18 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,7 +79,8 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the throughput and scale preset with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. +We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the <> with self monitoring enabled. +These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header] |=== |Resource | Throughput | Scale From 2a8e6d92398b822dde95ac31c4e2b258187cf6b0 Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Wed, 6 Nov 2024 12:51:27 +0200 Subject: [PATCH 14/17] Update the instance spec and with adjusted measurements Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index e47092c18..7e8f82ef1 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -79,15 +79,14 @@ Using our lab environment as an example, we can observe the following resource c === CPU and RSS memory size // lint ignore 2 vCPU 16.0 GiB -We tested using an AWS `m7i.xlarge` instance type with 4 vCPUs, 16.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the <> with self monitoring enabled. +We tested using an AWS `m7i.large` instance type with 2 vCPUs, 8.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the <> with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header] |=== -|Resource | Throughput | Scale -| **CPU*** | ~70% total | ~20% +|Resource | *Throughput* | *Scale* +| **CPU*** | ~67% total | ~20% | **RSS memory size*** | ~280 MB | ~220 MB -| **Write network throughput** | ~3.6 MB/s | 990 KB/s -| **Read network throughput** | ~40 KB/s | ~2.4 KB/s +| **Write network throughput** | ~3.5 MB/s | 480 KB/s |=== ^*^ including all monitoring processes From fce2cff8a09a7f24d660659baef02588326df6ad Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Wed, 6 Nov 2024 12:53:11 +0200 Subject: [PATCH 15/17] Formatting Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index 7e8f82ef1..e68b4d2c4 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -83,7 +83,7 @@ We tested using an AWS `m7i.large` instance type with 2 vCPUs, 8.0 GB of memory, These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header] |=== -|Resource | *Throughput* | *Scale* +| **Resource** | *Throughput* | *Scale* | **CPU*** | ~67% total | ~20% | **RSS memory size*** | ~280 MB | ~220 MB | **Write network throughput** | ~3.5 MB/s | 480 KB/s From 228074d75c1e3f44baaf94d96b229c3ea0da092a Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Wed, 6 Nov 2024 12:53:39 +0200 Subject: [PATCH 16/17] Make bold Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index e68b4d2c4..cde8b2079 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -83,7 +83,7 @@ We tested using an AWS `m7i.large` instance type with 2 vCPUs, 8.0 GB of memory, These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header] |=== -| **Resource** | *Throughput* | *Scale* +| **Resource** | **Throughput** | **Scale** | **CPU*** | ~67% total | ~20% | **RSS memory size*** | ~280 MB | ~220 MB | **Write network throughput** | ~3.5 MB/s | 480 KB/s From 0f3117db41c5a1ec809f96bf649d01632d1d1faa Mon Sep 17 00:00:00 2001 From: Alexandros Sapranidis Date: Thu, 7 Nov 2024 09:24:15 +0200 Subject: [PATCH 17/17] Fix lint ignore comment Signed-off-by: Alexandros Sapranidis --- .../elastic-agent/install-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc index cde8b2079..b32d79b43 100644 --- a/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc +++ b/docs/en/ingest-management/elastic-agent/install-elastic-agent.asciidoc @@ -78,7 +78,7 @@ Using our lab environment as an example, we can observe the following resource c [discrete] === CPU and RSS memory size -// lint ignore 2 vCPU 16.0 GiB +// lint ignore 2 vCPU 8.0 GiB We tested using an AWS `m7i.large` instance type with 2 vCPUs, 8.0 GB of memory, and up to 12.5 Gbps of bandwidth. The tests ingested a single log file using both the <> with self monitoring enabled. These tests are representative of use cases that attempt to ingest data as fast as possible. This does not represent the resource overhead when using {integrations-docs}/endpoint[{elastic-defend}]. [options,header]