diff --git a/daprdocs/content/en/concepts/faq.md b/daprdocs/content/en/concepts/faq.md
index 81e8d98b6..aaad28c0b 100644
--- a/daprdocs/content/en/concepts/faq.md
+++ b/daprdocs/content/en/concepts/faq.md
@@ -29,7 +29,7 @@ Read [How does Dapr work with service meshes?](https://github.com/dapr/dapr/wiki
 Istio is not a programming model and does not focus on application level features such as state management, pub-sub, bindings etc. That is where Dapr comes in.
 
 ## Performance Benchmarks
-The Dapr project is focused on performance due to the inherent discussion of Dapr being a sidecar to your application. This [performance benchmark video](https://youtu.be/4kV3SHs1j2k?t=783) discusses and demos the work that has been done so far. The performance benchmark data is planned to be published on a regular basis. You can also run the perf tests in your own environment to get perf numbers. 
+The Dapr project is focused on performance due to the inherent discussion of Dapr being a sidecar to your application. See [here]({{< ref perf-service-invocation.md >}}) for updated performance numbers.
 
 ## Actors
 
diff --git a/daprdocs/content/en/operations/performance-and-scalability/perf-service-invocation.md b/daprdocs/content/en/operations/performance-and-scalability/perf-service-invocation.md
index c33d4e2f6..0453aaeea 100644
--- a/daprdocs/content/en/operations/performance-and-scalability/perf-service-invocation.md
+++ b/daprdocs/content/en/operations/performance-and-scalability/perf-service-invocation.md
@@ -29,7 +29,7 @@ For more information see [overview of Dapr in self-hosted mode]({{< ref self-hos
 
 For more information see [overview of Dapr on Kubernetes]({{< ref kubernetes-overview.md >}}).
 
-## Performance summary for Dapr v0.11.3
+## Performance summary for Dapr v1.0
 
 The service invocation API is a reverse proxy with built-in service discovery to connect to other services. This includes tracing, metrics, mTLS for in-transit encryption of traffic, together with resiliency in the form of retries for network partitions and connection errors.
 
@@ -76,7 +76,7 @@ There are a number of variants that affect the CPU and memory consumption for ea
 ### Data plane performance
 
 The Dapr sidecar uses 0.48 vCPU and 23Mb per 1000 requests per second.
-End-to-end, the Dapr sidecars (client and server) add 1.57 ms to the 90th percentile latency, and 2.36 ms to the 99th percentile latency. End-to-end here is a call from one app to another app receiving a response. This is shown by steps 1-7 in [this diagram]({{< ref service-invocation-overview.md >}}).
+End-to-end, the Dapr sidecars (client and server) add ~1.40 ms to the 90th percentile latency, and ~2.10 ms to the 99th percentile latency. End-to-end here is a call from one app to another app receiving a response. This is shown by steps 1-7 in [this diagram]({{< ref service-invocation-overview.md >}}).
 
 ### Latency