[OAK-4081] Faster cost calculation for property indexes and traversal

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: property-index
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 02/Mar/16 08:02
• Updated: 27/Mar/17 05:04

Description

There are sometimes many property indexes, therefore cost calculation is slow. As seen in OAK-4076, we could re-order the indexes and stop once we found a good one (specially for unique indexes).

Also, currently we still check if traversal is faster than using an index. In many cases this check is not needed.

Issue Links

• is related to: OAK-3480 Query engine: faster cost calculation (take 2)
• is related to: OAK-2679 Query engine: faster cost calculation
• is related to: OAK-4076 Benchmark to measure affect of number of indexes on uuid lookup performance
• relates to: OAK-4904 For unique indexes avoid consulting indexes other than property index