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

Don't default to entitySelector of cacheType STEP for a selectionOrder=RANDOM changeMoveSelector

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • 6.3.0.CR1
    • None
    • optaplanner-core
    • None
    • This was fixed a few versions ago (not sure which version exactly, but before 6.3.0.CR1 definitely).

      This is a performance loss, especially if there are a lot of entities (100 000)

      <changeMoveSelector/>
      

      because the entitySelector ends up being cacheType=STEP and which calls SolutionDescriptor.getEntityListByPlanningEntityClass() every step!

      Workaround:

            <changeMoveSelector>
              <entitySelector>
                <cacheType>PHASE</cacheType>
              </entitySelector>
            </changeMoveSelector>
      

      Problem: We cannot make this the default if move's add/remove entities. We cannot make this the default in CH either.

              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

                Created:
                Updated:
                Resolved: