Blended · 5 weeks · blended
Performance Sanity for Busy Hosts
CPU, memory, and IO triage without chasing imaginary bottlenecks.
BRL 370 · informational only
Responsible mentor
Sofia Lemos
Lab reviewer who color-codes graphs with alarming cheer.
Program narrative
Profile politeness, interpret sar without superstition, and learn when to stop tuning. Labs include mentors sneaking noisy neighbors into your VMs.
Included drills
- sar reading sprints
- IO stack tracing with mentor hints
- Politeness rules for production-like captures
- Noise neighbor injection labs
- Written “stop tuning” criteria
- Peer review of flame-ish graphs
- Capacity note templates
Outcomes we expect you to evidence
- Justify a tuning stop with data
- Choose a profiling tool for a narrow question
- Explain IO wait without blaming users
FAQ for this track
Mentioned as a future path; not required to pass labs.
Experience notes
“Performance Sanity for Busy Hosts finally taught me when sar is enough and when I am procrastinating.”
— Marcos V. , DevOps junior · survey
“Noise neighbor labs were petty in the best way—mirrored our noisy neighbors on shared metal.”
— Tais · Recife · Edtech infra