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

[solver] Selector refactor: configurable subset selections, topList usage etc

    XMLWordPrintable

Details

    • Task
    • Resolution: Obsolete
    • Major
    • 5.5.0.Final
    • None
    • optaplanner-core
    • None

    Description

      Currently all moves are evaluated at every step (with a MaxAllForager at least) if you use the basic cached move factory selector.

      This doesn't scale well, especially for big data problems where in the beginning, just about every moves improves.
      The neighbourhood size (= amount of selected moves) could for example increase block-wise or timeGradient-wise until an improving solution is found.
      Notice the difference with the usage of FirstImprovingForager.

      Attachments

        Issue Links

          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: