Clarify the CPU/memory usage expectations of sidecars - Githubissues

istio / istio.io

Source for the istio.io site

https://istio.io/

Apache License 2.0

758 stars 1.5k forks source link

Clarify the CPU/memory usage expectations of sidecars #15335

Open craigbox opened 1 week ago

craigbox commented 1 week ago

https://istio.io/latest/docs/ops/deployment/performance-and-scalability/

In Istio 1.21, a proxy consumes about 0.5 vCPU per 1000 requests per second.

@howardjohn suggests this isn't necessarily true, or at the least it has not been updated for a very long time.

See how we changed between:

https://istio.io/v1.16/docs/ops/deployment/performance-and-scalability/ (0.35 vCPU and 40 MB memory)
https://istio.io/v1.17/docs/ops/deployment/performance-and-scalability/ (404)
https://istio.io/v1.18/docs/ops/deployment/performance-and-scalability/ (rewritten to lose the nuance and just retain the 0.5 vCPU meme)

See also

howardjohn commented 1 week ago

Did some quick tests:

1k qps: .18vCPU
2k qps: .3vCPU
3k qps: .4vCPU
4k qps: .43vCPU
5k qps: .45vCPU

Not sure how to convey this non-linear scaling