Automatic

Your OS defaults were designed for nobody in particular — and your production workload isn't nobody. This episode breaks down kernel tuning: what to measure, which levers move the needle, and how to make performance gains that actually stick.

Show Notes

Default kernel settings are a compromise built for generic hardware and fictional average workloads. For teams running automation, high-traffic services, or latency-sensitive pipelines, those defaults aren't neutral — they're a quiet, compounding tax on every request your system handles. This episode of Automatic draws on the kernel tuning deep-dive article to make the case that treating OS parameters as a set-and-forget concern is one of the most expensive habits in infrastructure.

The episode walks through the full arc of a rigorous tuning practice — from understanding why defaults exist to knowing which knobs are worth touching and how to touch them safely. Key topics covered include:

  • Why defaults cost you: Kernel parameters are optimized for predictability over performance, quietly draining capacity across networking, memory, I/O, and CPU scheduling — often before application code even runs.
  • The four high-leverage categories: CPU scheduling (reducing context switches and preserving cache locality), memory and swappiness (preventing silent swap storms), I/O queue depth and scheduler selection (feeding modern NVMe storage properly), and TCP buffer tuning (handling burst traffic without dropped packets).
  • Measurement before everything: Establishing a clean baseline — covering tail latency, run-queue depth, swap activity, retransmits, and more — before a single parameter is changed.
  • One change at a time: Why stacking adjustments before understanding each one individually is how tuning efforts go wrong, and how a disciplined iterate-and-revert workflow keeps gains trustworthy.
  • Rollback as a non-negotiable: Encoding every change in configuration management and shipping it through the same pipeline as application releases, turning tuning into a routine practice with a clean audit trail.
  • Tuning as ongoing habit: Kernels and workloads both evolve — the episode makes the case for a living catalog of changes, continuous integration for key tests, and incremental monthly wins over high-risk one-time heroics.

The episode also addresses a common misconception: that security and stability must be traded away for performance. Good tuning preserves both — the best-tuned systems look boring on a dashboard, and boring at 2 a.m. is exactly the goal. For a companion listen, check out The Anatomy of a Secure AI Knowledge Base, which explores how performance and security considerations intersect in AI infrastructure. The full technical write-up behind this episode is linked above.

Automatic.co

What is Automatic?

Agentic AI and automation from the perspective of whoever has to maintain it in six months. Where an agent genuinely belongs in a process, where a plain script is enough, how to design a handoff to a human, and what breaks quietly at scale.

Each episode takes one automation decision and reasons it through end to end — including the maintenance burden, the failure modes and the honest question of whether the process should exist at all. Written for operators and technical leads, deliberately free of hype. Five or six minutes an episode.

Topics include where an agent belongs versus a plain script, designing human handoffs, error handling and observability, maintenance burden, process mapping before automation, measuring what a workflow saves, and knowing when a process should be deleted instead.

Produced by Automatic.co, agentic AI and automation consulting. Full details, services and further reading at https://automatic.co