Rick Rackow
summary
A small Go program moves from serial to concurrent to parallel code and the demos show concrete timings: the binary runs ~2.9s on the host and inside Docker until GOMAXPROCS is lowered, when setting GOMAXPROCS=4 doubles runtime for eight CPU‑bound tasks, proving concurrency ≠ parallelism. The build uses a multi‑stage Dockerfile and minikube for Kubernetes testing, where containers report 10 CPUs and Kubernetes CPU requests/limits get rounded so fractional CPU requests round up to whole cores, causing unexpected GOMAXPROCS values.
AI-written summary · about
chapters (14)
- 0:00Introduction and setup
- 1:12Speaker introduction
- 1:55Key questions about Go
- 3:01Sequential to concurrent execution
- 5:08Go routines behavior demo
- 7:21Go max procs and CPU limits
- 11:40Go in containers overview
- 13:07Docker container demo
- 18:25Kubernetes CPU limits
- 23:11MiniKube setup issues
- 24:15Go max procs in Kubernetes
- 27:22Summary of demos
- 28:48Takeaways and conclusions
- 29:32Q&A session
