[OAK-1999] Query engine is slow when using many "or" constraints

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.0.1, 1.0.2
• Fix Version/s: 1.0.4, 1.1.0
• Component/s: query
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 29/Jul/14 10:26
• Updated: 01/Oct/14 13:07
• Resolved: 29/Jul/14 11:36

Description

For queries with many (300 or so) "or" constraints of the form "x = 1 or x = 2 or x = 3", the query engine uses quite a lot of CPU time. According to profiling data, this is due to using "toString()" too often, and "Sets.union" (com.google.common.collect.Sets).

The Oak 1.0 branch is affected most, not sure about trunk.