From 892bbadc917f008e004f577372711247aa6e138a Mon Sep 17 00:00:00 2001 From: Yaron Schneider Date: Tue, 16 Feb 2021 14:54:02 -0800 Subject: [PATCH] add sm perf remark (#1229) --- .../performance-and-scalability/perf-service-invocation.md | 2 ++ 1 file changed, 2 insertions(+) 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 0453aaeea..8ba7ba02e 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 @@ -78,6 +78,8 @@ There are a number of variants that affect the CPU and memory consumption for ea 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.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 >}}). +This performance is on par or better than commonly used service meshes. + ### Latency In the test setup, requests went through the Dapr sidecar both on the client side (serving requests from the load tester tool) and the server side (the target app).