[OAK-4558] SegmentNodeState.fastEquals() can trigger two I/O operations

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Later
• Component/s: segment-tar
• Labels: performance
• Epic Link: TarMK content scalability
• Assignee: Francesco Mari
• Reporter: Francesco Mari
• Created: 14/Jul/16 09:08
• Updated: 26/Feb/18 12:41
• Resolved: 26/Feb/18 12:41

Description

The implementation of SegmentNodeState.fastEquals() compares the stable IDs of two instances of SegmentNodeState. In some cases, reading the stable ID would trigger a read of an additional record, the block record containing the serialized version of the segment ID.

This issue is about evaluating the performance implications of this strategy and, in particular, if it would be better to store the serialized stable ID in the node record itself.

Issue Links

• is related to: OAK-5655 TarMK: Analyse locality of reference