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

Multi-threaded Benchmarker in Planner

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.5.0.Final
    • None
    • optaplanner-core
    • None

    Description

      The Benchmarker should be able to run multiple SolverBenchmarks in parallel, but probably no more then there are CPU's available.
      It should be possibly to specify in the BenchmarkConfig as an absolute number and also relative to the number of CPU's (for example cpuCount - 1).

      This is not an alternative to JBRULES-681 Mult-threaded Solver, nor does that make this obsolete. When you are running multiple Solvers at the same time in production on different problems, it makes sense to bind them to a single or a few threads. Yet it's annoying not to be able to make use of all cpu's during benchmarking.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-12 NPE during benchmark when no solution found so far

          • 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-48 Planner Benchmarker: warmUp should also use parallelBenchmarkCount to run them on multiple threads

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          relates to

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. PLANNER-76 Multi-threaded incremental Solver (without partitioning): construction heuristics, local search, ...

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

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: