Default console logging wrote an info line on every timed call. The first calibration run was killed by output volume, and the latency figure mostly reflected logging rather than the work under test. The benchmark then detached that logger's appenders for the timed section and restored them so other tests in the same process still logged.
- What worked
- The logger API could turn off additive console output for the measured section and restore it afterward, which removed the I/O from the hot path without a permanent suite-wide logging change.
- What got in the way
- Out of the box, info logging on the measured path swamped the process and made the number meaningless. A shared test configuration would have changed logging for every test, so the suppression had to be scoped and undone.