[JBoss JIRA] (DROOLS-676) Optional SortedMap semantics for matching
by Paul Houle (JIRA)
Paul Houle created DROOLS-676:
---------------------------------
Summary: Optional SortedMap semantics for matching
Key: DROOLS-676
URL: https://issues.jboss.org/browse/DROOLS-676
Project: Drools
Issue Type: Feature Request
Affects Versions: 6.2.0.CR3
Environment: any
Reporter: Paul Houle
Assignee: Mark Proctor
Drools uses a Map instead of a SortedMap to accelerate the matching of patterns that have an equality relationship. Performance-wise this is the right decision most of the time, but if one wanted to accelerate matching of patterns such as
Person(age > 100)
having a sorted index could be beneficial. In a case like that the object in question must implement Comparable or be associated with a Comparator. This behavior could be turned on for a particular field with @-annotation in either the DRL or Java file.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (DROOLS-675) Query Optimization for RHS by changing pattern match order
by Paul Houle (JIRA)
Paul Houle created DROOLS-675:
---------------------------------
Summary: Query Optimization for RHS by changing pattern match order
Key: DROOLS-675
URL: https://issues.jboss.org/browse/DROOLS-675
Project: Drools
Issue Type: Enhancement
Affects Versions: 6.2.0.CR3
Environment: any
Reporter: Paul Houle
Assignee: Mark Proctor
I've been using Drools for what I consider "small" semantic databases, right now in the range of 1M-10M facts but that could get bigger.
One thing I notice is that performance is dependent on the order that I put patterns in the RHS; if the high selectivity patterns go first I am happy with the results but put them in the wrong order and gee wiz, I won't wait long enough for it to try all the matches that fail.
I see Drools as competitive with products such as triple stores, deductive databases and many of them have this feature
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months