mirror of https://github.com/dapr/docs.git
add sm perf remark (#1229)
This commit is contained in:
parent
b162c3df9e
commit
892bbadc91
|
@ -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).
|
||||
|
|
Loading…
Reference in New Issue