Going FaaSter: Cost-Performance Optimizations of Serverless on Kubernetes
summary
Walks through concrete runtime fixes for cold starts using Fission on Kubernetes and general FaaS models, showing four actionable optimizations: instance reuse, stem-cell pooling to avoid runtime startup, artifact prefetching, and predictive pre-warming. Compares tradeoffs like concurrency=1 vs 50 (more isolation yields more cold starts), public clouds keeping containers alive for hours to days versus Kubernetes systems that tear them down in minutes, and notes pooling creates a visible fixed cost rather than per-invocation billing.
AI-written summary · about
chapters (4)
- 0:00Start
- 10:45Function Resource Reuse
- 15:16Optimization 2 Function Runtime Pooling
- 18:40Optimization 3 Function Prefetching
related talks
37mGo FaaSter: Cold Start Optimization in a Serverless Platform
37mGo FaaSter: Cold Start Optimization in a Serverless Platform
27mServerless Performance on a Budget
39mFaaS: A Contemporary, Comparative Study
33mFission: Serverless Functions for Kubernetes
36mFission: a Serverless Function Framework on Kubernetes [B]
34mServerless Operations: From Dev to Production
21mWhat is the Future of Serverless Computing?
