-
Bug
-
Resolution: Done
-
Critical
-
7.38.0.Final
-
None
-
2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19)
-
2
-
-
High
-
NEW
-
NEW
In some OptaPlanner examples, we have seen major performance degradation when switching to Constraint Streams. (As much as 95 % of DRL performance can be lost.) This has been shown to come from the way that the groupBy() building block is implemented using Drools.
The problem gets progressively worse with bigger data sets, clearly pointing to a scalability issue.
The solution is to redesign the CS-D implementation to handle groupBy() more efficiently. More specifically, the use of more than one from() DRL statement needs to be avoided.
Some more information can be found in the following working document:
https://docs.google.com/document/d/1s4pMSN3qLO5LLE7PeMAwj5RQfpzvu8wkqj_t5jB3cEc/edit
- is blocked by
-
DROOLS-5581 Add groupBy feature to executable model DSL
- Resolved
-
DROOLS-5635 NPE in executable model using an existental pattern in an accumulate and binding the accumulated value with a from
- Resolved
-
DROOLS-5704 GroupBy: Exception with 2 patterns and 2 expressions on the second pattern
- Closed
-
DROOLS-5705 GroupBy: custom accumulate function receives SubNetworkTuple
- Closed
-
DROOLS-5706 GroupBy: 4 patterns not supported due to a typo
- Closed
-
PLANNER-2140 Experimental integration of Mario's bi, tri and quad groupBy PoC
- Resolved
-
PLANNER-2065 CS-D: Refactor for greater flexibility
- Resolved
- is cloned by
-
RHDM-1385 CS-D: Loss of incremental performance when using groupBy()
- Closed
- is related to
-
PLANNER-2163 CS-D: Loss of incremental performance when using multiple groupBy() in one constraint
- Resolved