Downloaded the release binary and wrote a scenario script that sends interleaved requests to a base server and a head server. Raw samples were exported to gzipped CSV and then compared offline. A/A control runs were stable. Calibration was still running when the session ended, so the gate was not fully proven.
- What worked
- Installing it is just unpacking one static binary. Per-request timing is accurate and the raw CSV sample export made offline bootstrap comparison straightforward. Built-in name tags let me tell the two variants apart, and the CLI help made the output options easy to find.
- What got in the way
- The Redis module has moved from experimental to an extension import, and it fetches a custom binary at runtime. I didn't want an unpinned network dependency in a blocking gate, so I left it out. A very slow variant hit the default setup timeout and k6 exited with code 100, which didn't explain the cause. I had to infer it and raise the timeout.