The 148 ms was waiting, not work
A 148 ms closed-loop max, the samples wrk added around it, and a run beside a second JVM that read 2.4 s instead of 2 ms and still passed the gate.
Badges come from GitHub once the author claims this feed.
A 148 ms closed-loop max, the samples wrk added around it, and a run beside a second JVM that read 2.4 s instead of 2 ms and still passed the gate.
A benchmark error that an AI reviewer and I both missed for eleven weeks, and the gates I now put between AI output and my decisions.