Performance tuning and best practices in a Knative based, large-scale serverless platform with Istio
in a Knative based platform ● Performance bottleneck analysis and tuning ○ Istio scalability optimization during Knative Service provisioning ○ Unleash maximum scalability by fully leveraging Istio features MEM Knative Version Knative 0.16, 0.17, 0.18 Istio Version 1.5, 1.6, 1.7 Istio scalability optimization during Knative Service provisioning • Benchmark: Kperf (https://github.com/knative-sandbox/kperf) resolved this issue. o Istiod MEM bumped with large numbers of Knative Services (#25532) Mem usage optimization of pilot resolved this issue. • Tune CPU/MEM to ensure enough capacity Leveraged Metrics to0 码力 | 23 页 | 2.51 MB | 1 年前3CppCon2021 Concurrency TS2
• Domains: • Robust default domain with expanded capabilities (cohorts, link counting, array optimization). • No customization needed in Folly so far. 24 © 2021. 25 Hazard Pointers Proposal for C++26 hazard_pointer&) noexcept; 29 © 2021. 30 Hazard Pointers Beyond C++26 • Hazard pointer array optimization • In heavy use in Folly for ~4 years. Simple. • Synchronous reclamation • Folly cohort synchronous0 码力 | 58 页 | 1.62 MB | 5 月前0.03Apache Cassandra™ 10 Documentation February 16, 2012
causes: • Row cache is too large, or is caching large rows • Row cache is generally a high-end optimization. Try disabling it and see if the OOM problems continue. • The memtable sizes are too large for0 码力 | 141 页 | 2.52 MB | 1 年前3
共 3 条
- 1