In progress

Part 21 - Go Scheduler Internals: How Many Workers Should the Pipeline Run?

Every worker pool in this series has a -workers flag, and so far we have picked its value by feel. Part 21 opens Arc 3 by looking under the hood at the M:P:G scheduler and measuring why LLM calls scale far past your CPU count while CPU-bound work stops dead at GOMAXPROCS.

This post is still being written. The title and outline are published so you can follow along with the series — the full article will replace this page when it ships.