You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/07/14 09:09:20 UTC

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

Francesco Mari created OAK-4558:
-----------------------------------

             Summary: 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: Bug
          Components: segment-tar
            Reporter: Francesco Mari
            Assignee: Francesco Mari
             Fix For: Segment Tar 0.0.6


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.3.4#6332)