[OAK-4797] Optimise stable ids

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: segment-tar
• Labels: memory performance
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 12/Sep/16 14:51
• Updated: 17/Oct/16 10:16
• Resolved: 17/Oct/16 10:16

Description

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.