OSSMDOC-581: resolved merge conflict

Author: rh-tokeefe

modules/ossm-load-test-results.adoc

@@ -7,11 +7,11 @@ This module included in the following assemblies:
 = Load test results
 
 The upstream Istio community load tests mesh consists of *1000* services and *2000* sidecars with 70,000 mesh-wide requests per second.
-Running the tests using Istio 1.6.8, generated the following results:
+Running the tests using Istio 1.12.3, generated the following results:
 
-* The Envoy proxy uses *0.5 vCPU* and *50 MB memory* per 1000 requests per second going through the proxy.
+* The Envoy proxy uses *0.35 vCPU* and *40 MB memory* per 1000 requests per second going through the proxy.
 * Istiod uses *1 vCPU* and *1.5 GB* of memory.
-* The Envoy proxy adds *3.12 ms* to the 90th percentile latency.
+* The Envoy proxy adds *2.65 ms* to the 90th percentile latency.
 * The legacy `istio-telemetry` service (disabled by default in Service Mesh 2.0) uses *0.6 vCPU* per 1000 mesh-wide requests per second for deployments that use Mixer.
 // TODO The Envoy numbers goes down in 1.9, check for the latest data with next version of Istio.
 The data plane components, the Envoy proxies, handle data flowing through the system. The control plane component, Istiod, configures the data plane. The data plane and control plane have distinct performance concerns.
@@ -52,7 +52,7 @@ The latency, throughput, and the proxies' CPU and memory consumption are measure
 
 === CPU and memory consumption
 
-Since the sidecar proxy performs additional work on the data path, it consumes CPU and memory. As of Istio 1.1, a proxy consumes about 0.6 vCPU per 1000 requests per second.
+Since the sidecar proxy performs additional work on the data path, it consumes CPU and memory. As of Istio 1.12.3, a proxy consumes about 0.5 vCPU per 1000 requests per second.
 //TODO As of Istio 1.7, a proxy consumes about 0.5 vCPU per 1000 requests per second.
 
 The memory consumption of the proxy depends on the total configuration state the proxy holds.
@@ -72,4 +72,4 @@ However, since the worker is busy handling the request, the worker won't start h
 This process adds to the queue wait time of the next request and affects average and tail latencies.
 The actual tail latency depends on the traffic pattern.
 
-Inside the mesh, a request traverses the client-side proxy and then the server-side proxy. In the default configuration of Istio 1.6.8 (that is, Istio with telemetry v2), the two proxies add about 3.12 ms and 3.13 ms to the 90th and 99th percentile latency, respectively, over the baseline data plane latency.
+Inside the mesh, a request traverses the client-side proxy and then the server-side proxy. In the default configuration of Istio 1.12.3 (that is, Istio with telemetry v2), the two proxies add about 1.7 ms and 2.7 ms to the 90th and 99th percentile latency, respectively, over the baseline data plane latency.