[ https://issues.apache.org/jira/browse/OAK-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated OAK-4558: ------------------------------- Fix Version/s: (was: 1.8) > SegmentNodeState.fastEquals() can trigger two I/O operations > ------------------------------------------------------------ > > Key: OAK-4558 > URL: https://issues.apache.org/jira/browse/OAK-4558 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar > Reporter: Francesco Mari > Assignee: Francesco Mari > Priority: Minor > Labels: performance > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)