|
| 1 | +// Module included in the following assemblies: |
| 2 | +// * network_observability/configuring_operator.adoc |
| 3 | + |
| 4 | +:_mod-docs-content-type: REFERENCE |
| 5 | +[id="network-observability-total-resource-usage-table_{context}"] |
| 6 | += Total average memory and CPU usage |
| 7 | + |
| 8 | +The following table outlines averages of total resource usage for clusters with a sampling value of 1, 50, and 400 for 3 different tests: `Test 1`, `Test 2`, and `Test 3`. The tests differ in the following ways: |
| 9 | + |
| 10 | +- `Test 1` takes into account the total number of namespace, pods and services in an {product-title} cluster, places load on the eBPF agent, and represents use cases with a high number of workloads for a given cluster size. For example, `Test 1` consists of 76 Namespaces, 5153 Pods, and 2305 Services. |
| 11 | +- `Test 2` takes into account a high ingress traffic volume. |
| 12 | +- `Test 3` takes into account the total number of namespace, pods and services in an {product-title} cluster, places load on the eBPF agent on a larger scale than `Test 1`, and represents use cases with a high number of workloads for a given cluster size. For example, `Test 3` consists of 553 Namespaces, 6998 Pods, and 2508 Services. |
| 13 | +
|
| 14 | +Since different types of cluster use cases are exemplified in the different tests, the numbers in this table cannot be linearly compared side-by-side, but instead are intended to be used as a benchmark for evaluating your personal cluster usage. The examples outlined in the table demonstrate scenarios that are tailored to specific workloads. Consider each example only as a baseline from which adjustments can be made to accommodate your workload needs. |
| 15 | + |
| 16 | +[NOTE] |
| 17 | +==== |
| 18 | +Metrics exported to Prometheus can impact the resource usage. Cardinality values for the metrics can help determine how much resources are impacted. For more information, see "Network Flows format" in the Additional resources section. |
| 19 | +==== |
| 20 | + |
| 21 | +.Total average resource usage |
| 22 | +[%autowidth, options="header"] |
| 23 | +|=== |
| 24 | +| Sampling value | Parameters | Test 1 (25 nodes) | Test 2 (65 nodes) | Test 3 (120 nodes) |
| 25 | +.6+| *Sampling = 1* | *With Loki* 3+| |
| 26 | +| Total NetObserv CPU Usage | 3.24 | 3.42 | 7.30 |
| 27 | +| Total NetObserv RSS (Memory) Usage | 14.09 GB | 22.56 GB | 36.46 GB |
| 28 | +| *Without Loki* 3+| |
| 29 | +| Total NetObserv CPU Usage | 2.40 | 2.43 | 5.59 |
| 30 | +| Total NetObserv RSS (Memory) Usage | 6.85 GB | 10.39 GB | 13.92 GB |
| 31 | +.6+| *Sampling = 50* | *With Loki* 3+| |
| 32 | +| Total NetObserv CPU Usage | 2.04 | 2.36 | 3.31 |
| 33 | +| Total NetObserv RSS (Memory) Usage | 8.79 GB | 19.14 GB | 21.07 GB |
| 34 | +| *Without Loki* 3+| |
| 35 | +| Total NetObserv CPU Usage | 1.55 | 1.64 | 2.70 |
| 36 | +| Total NetObserv RSS (Memory) Usage | 6.71 GB | 10.15 GB | 14.82 GB |
| 37 | +.6+| *Sampling = 400* | *With Loki* 3+| |
| 38 | +| Total NetObserv CPU Usage | 1.71 | 1.44 | 2.36 |
| 39 | +| Total NetObserv RSS (Memory) Usage | 8.21 GB | 16.02 GB | 17.44 GB |
| 40 | +| *Without Loki* 3+| |
| 41 | +| Total NetObserv CPU Usage | 1.31 | 1.06 | 1.83 |
| 42 | +| Total NetObserv RSS (Memory) Usage | 7.01 GB | 10.70 GB | 13.26 GB |
| 43 | +|=== |
| 44 | + |
| 45 | + |
| 46 | +Summary: This table shows average total resource usage of Network Observability (Agents+FLP+Kafka+Loki). |
0 commit comments