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

Selectors should support cacheType SOLVER with DroolsScoreDirector and IncrementalScoreDirector too: reuse multi-threading id technology to migrate the selector cache to the new solution clone

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Optional
    • Future
    • None
    • optaplanner-core

    Description

      Selector cacheType solver doesn't work because between phases, the bestSolution is set as the workingSolution and entities get cloned. Therefor the cached moves are pointing to the old entities which haven't been inserted into the new Drools Expert working memory.

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement or refactoring of existing functionality PLANNER-221 Performance bottleneck: do not default EntitySelectors to cacheType STEP if the entity count is stable

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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PLANNER-76 Multi-threaded incremental Solver (without partitioning): construction heuristics, local search, ...

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

          Activity

            People

              Unassigned Unassigned
              gdesmet@redhat.com Geoffrey De Smet
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: