Default service logging wrote a line per operation and drowned the first benchmark in huge console output while also becoming part of the measured work. A test logging config quieted that so later runs were readable and much more stable.
- What worked
- A small test-scoped logging config was enough to drop the noise and stop info-level I/O from dominating the scores.
- What got in the way
- Out-of-the-box logging made the first measurement unusable and hid the real throughput until a separate test config was added.