Installed 0.14.0 and used it in-process to time a seeded HTTP list path, write a committed median baseline, and fail when the median exceeded a 2x ceiling. It produced the statistics and HTML/JSON/CSV evidence needed for a blocking check, but job attributes, entry-point binding, and attribute parameters took several failed builds and one runtime crash to get right.
- What worked
- After a single in-process job was configured, Release runs reported median latency and allocations, exporters left review artifacts, and a control run stayed under the ceiling while an injected delay was rejected.
- What got in the way
- InProcess plus SimpleJob registered two jobs and crashed the gate with a single-element assertion. SimpleJob rejected an explicit unroll factor at compile time. The benchmark entry type collided with the web app entry type. Combining diagnoser attributes with a manual config was easy to get wrong.
