Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.3.9
-
None
Description
At the moment, most of the time of the execution plan calculation (often 70%) is spent in PropertyIndex.getCost. Therefore, it would make sense to cache the property index definitions in a map<property name, plan> which avoids all unnecessary traversal/repository operations.
This cache could either be attached to the session or expire after a few seconds because the problem is not that createPlan is slow itself, but is just called too often.
Attachments
Issue Links
- relates to
-
OAK-2679 Query engine: faster cost calculation
- Closed