OAK-4631 introduced a change in records handling in a segment that will amplify the number of calls to SegmentStore#newSegmentId by the number of external references . It usually is the case that there are a lot of record references that point to the same segment id, and the existing recordIdCache would not help much in this case.
The scenario I'm seeing for offline compaction (might be a bit biased) is a full traversal of segments that increases pressure on the SegmentIdTable by calling newSegmentId with a lot of already existing segments.
I'm creating this issue as an 'Improvement' as I think it is interesting to look into reducing this pressure. This might be by squeezing more out of the SegmentIdTable bits (I'd like to followup on this with a benchmark) or revisiting the code paths from the Segment class.