[ https://issues.apache.org/jira/browse/OAK-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dürig updated OAK-4797: ------------------------------- Fix Version/s: (was: Segment Tar 0.0.14) Segment Tar 0.0.16 > Optimise stable ids > -------------------- > > Key: OAK-4797 > URL: https://issues.apache.org/jira/browse/OAK-4797 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: segment-tar > Reporter: Michael Dürig > Assignee: Michael Dürig > Labels: memory, performance > Fix For: Segment Tar 0.0.16 > > > Currently {{SegmentNodeState#getStableId()}} returns a string with all its > associated overhead: > * high memory requirements (42 characters plus the overhead of a {{String}} > instance. The raw requirements are a mere 20 bytes (long msb, long lsb, int > offset). The memory overhead is problematic as the stable id is used as key > in the node deduplication cache (See OAK-4635). > * high serialisation cost. I have seen {{getStableId()}} occurring in stack > traces. This is to be expected as that method is called quite often when > comparing node states. > This issue is to explore options for reducing both CPU and memory overhead of > stable ids. -- This message was sent by Atlassian JIRA (v6.3.4#6332)