https://tsvinc.dev/tags/devops/ Recent content in Devops on tsvinc Hugo en-us Thu, 02 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/200-vus-vs-nasa-demo-key/ Thu, 02 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/200-vus-vs-nasa-demo-key/ <p>The fix for exit 123 was one <code>sed</code>. It took the crash away, and the crash had been the only thing standing between a load generator and <code>api.nasa.gov</code>.</p> <h2 id="the-branch-map-nobody-filtered">The Branch Map Nobody Filtered<a class="heading-anchor" href="#the-branch-map-nobody-filtered" aria-label="Link to section: The Branch Map Nobody Filtered">#</a></h2><p>The benchmark suite has twenty-four branches. Eighteen are &quot;synth&quot; branches: their <code>*-synth-*</code> scenario scripts add a <code>docker-compose-synth.yml</code> overlay to <code>COMPOSE_FILE</code>, which starts a Go mock server and points every client at it. From the Micronaut overlay:</p> https://tsvinc.dev/posts/four-exit-codes-benchmark/ Thu, 02 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/four-exit-codes-benchmark/ <p>The orchestrator reported ALL_DONE after one branch. The map held fourteen branches and 36 scenarios.</p> <p>Twenty-four framework branches. Docker Compose up, k6 ramp to 200 VUs, Prometheus scrape, tear down, next branch. The loop script is a few dozen lines of bash — read a branch map, check out worktrees, run <code>benchmark-all.sh</code>, collect results. None of this is complicated, which is exactly why all four bugs took so long to find.</p>