MVCCIterator.Stats() has been seen to use ~4% of CPU during MVCCGet benchmarks:

This is used to attach iterator stats to a running trace, but the stats collection is called unconditionally (regardless of whether an actual trace is in progress):

Jira issue: CRDB-18562