Update Performance and Scalability Page for 1.8 (#8574)

content/en/docs/ops/deployment/performance-and-scalability/index.md

@@ -37,9 +37,9 @@ The [Istio load tests](https://github.com/istio/tools/tree/{{< source_branch_nam
 of **1000** services and **2000** sidecars with 70,000 mesh-wide requests per second.
 After running the tests using Istio {{< istio_release_name >}}, we get 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 2.76 ms to the 90th percentile latency.
+- The Envoy proxy adds 2.65 ms to the 90th percentile latency.
 
 ## Control plane performance
 
@@ -115,8 +115,8 @@ section, we will present both `jitter` and `non-jitter` performance measurements
 
 Inside the mesh, a request traverses the client-side proxy and then the server-side
 proxy. In the default configuration of Istio {{< istio_release_name >}} (i.e. Istio with telemetry v2),
-the two proxies add about 2.76 ms and 2.88 ms to the 90th and 99th percentile latency, respectively, over the baseline data plane latency.
-After enabling `jitter`, those numbers reduced to 1.72 ms and 1.91 ms, respectively. We obtained these results using the [Istio benchmarks](https://github.com/istio/tools/tree/{{< source_branch_name >}}/perf/benchmark)
+the two proxies add about 2.65 ms and 2.91 ms to the 90th and 99th percentile latency, respectively, over the baseline data plane latency.
+After enabling `jitter`, those numbers reduced to 1.7 ms and 2.69 ms, respectively. We obtained these results using the [Istio benchmarks](https://github.com/istio/tools/tree/{{< source_branch_name >}}/perf/benchmark)
 for the `http/1.1` protocol, with a 1 kB payload at 1000 requests per second using 16 client connections, 2 proxy workers and mutual TLS enabled.
 
 {{< image width="90%"