[OAK-2679] Query engine: faster cost calculation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.7, 1.4
• Component/s: core, query
• Labels: performance
• Epic Link: Query performance improvements
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 25/Mar/15 13:16
• Updated: 16/Feb/21 09:55
• Resolved: 25/Sep/15 06:32

Description

If there are many indexes, preparing a query can take a long time, in relation to executing the query.

The query execution plans can be cached. The cache should be invalidated if there are new indexes, or indexes are changed; a simple solution might be to use a timeout, and / or a manual cache clean via JMX or so.

Issue Links

• is related to: OAK-3600 Cache property index definitions
• is related to: OAK-2263 Avoid unnecessary reads on index lookup
• relates to: OAK-3480 Query engine: faster cost calculation (take 2)
• relates to: OAK-2777 Minimize the cost calculation for queries using reference restrictions.
• relates to: OAK-4081 Faster cost calculation for property indexes and traversal