Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-2003

CS-D: Loss of incremental performance when using groupBy()

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 8.0.0.Final
    • 7.38.0.Final
    • optaplanner-core
    • None
    • 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19)
    • 2
    • Hide

      There is no workaround.

      Show
      There is no workaround.
    • High
    • NEW
    • NEW

    Description

      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

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users DROOLS-5581 Add groupBy feature to executable model DSL

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-5635 NPE in executable model using an existental pattern in an accumulate and binding the accumulated value with a from

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-5704 GroupBy: Exception with 2 patterns and 2 expressions on the second pattern

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-5705 GroupBy: custom accumulate function receives SubNetworkTuple

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-5706 GroupBy: 4 patterns not supported due to a typo

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2140 Experimental integration of Mario's bi, tri and quad groupBy PoC

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-2065 CS-D: Refactor for greater flexibility

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1385 CS-D: Loss of incremental performance when using groupBy()

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-2163 CS-D: Loss of incremental performance when using multiple groupBy() in one constraint

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              lpetrovi@redhat.com Lukáš Petrovický (Inactive)
              lpetrovi@redhat.com Lukáš Petrovický (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: