New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify the CPU/memory usage expectations of sidecars #15335

Open

craigbox opened this issue Jun 26, 2024 · 1 comment

Assignees

Contributor

craigbox commented Jun 26, 2024

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

craigbox assigned howardjohn

Member

howardjohn commented Jun 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment