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

Performance regression related to Partitioned Search feature (micro benchmarks)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.7.0.Final
    • 7.0.0.Beta4
    • optaplanner-core
    • None
    • 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06
    • NEW
    • NEW

    Description

      QE benchmarks showed performance regression after merging PLANNER-491. Details and numbers are in the product planning JIRA.

      This issue is to track the investigation progress.

      This happened when something landed between 8-nov-2016 and 21-nov-2016 (inclusive) on 7.x:
      http://perfrepo.mw.lab.eng.bos.redhat.com/reports/metric/9873

      This is suspect A):
      https://github.com/kiegroup/optaplanner/commit/c942371bf739
      Other commits have not been removed from the suspect list.

      Attachments

        1. Selection_597.png
          126 kB
          Geoffrey De Smet
        2. Selection_598.png
          169 kB
          Geoffrey De Smet

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-694 FieldAccessingSolutionCloner should be thread safe because it changes state after creation

          • 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 related to

          Feature Request - Feature requests from customers and/or users PLANNER-491 Partitioned Search

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          relates to

          Task - Represents a small unit of work that is not end-user facing. PLANNER-924 Performance report: 7.5.0-SNAPSHOT vs 6.5.0.Final (macro benchmark)

          • 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

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              jlocker Jiří Locker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: