[OAK-663] oak-jcr performance optimization

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.11
• Component/s: jcr
• Labels: performance
• Assignee: Unassigned
• Reporter: Jukka Zitting
• Created: 28/Feb/13 22:30
• Updated: 21/Nov/13 10:30
• Resolved: 11/Nov/13 19:04

Description

Currently oak-jcr does a lot of unnecessary work for various reasons. This is a major drag on performance.

For example, a getString() call on an already acquired PropertyImpl instance (with no refresh() or other operations in between) requires 12 NodeBuilder.getProperty() calls to access that same property state over and over again.

Issue Links

• is blocked by: OAK-908 Performance measurement
• relates to: OAK-672 Avoid JCR APIs calling other JCR APIs

Sub-Tasks

• Optimise TreeImpl.getBaseState(): Closed
• Optimize Session.getNamespacePrefixes(): Closed
• Optimize access to node type information: Closed
• Optimize namespace lookups: Closed
• Optimise path parsing: Closed
• Optimise Session.getNode: Closed