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

NonUniqueNotificationVariableListener to forgo unique notification requirement in favor of performance gain

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Critical
    • 7.0.0.Beta2
    • 6.3.0.Final
    • optaplanner-core
    • None
    • NEW
    • NEW

    Description

      There is a guarantee that the every notification to a VariableListener is unique. For example beforeVarChange(Paris) won't be called twice in the same move. This is interesting for when a shadow variable depends on 2 planning variable or for certain (custom) moves that might change the same entity twice (not applicable to CompositeMove).

      That uniqueness guarantee can be costly, for example in VRPTW for reversing chain moves. A VariableListener can be implemented to gracefully ignore non-unique notifications (without having to keep a Set), by simply doing nothing if the shadow variable is already in the deterministic state. If the VariableListener implements a new tagging interface, then VariableListenerNotifiable can use a List instead of a Set for the notificationQueue.

      (Based by Jiri's feedback)

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-252 VariableListeners for shadow variables that are triggered on other shadow variables should be triggered predictably in a smart order

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

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-479 TailChainSwapMove's reverseChain() seems to cause a performance loss since 6.3.0.CR1

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

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2809 Deprecate VariableListener#requiresUniqueEntityEvents

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Open

          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-481 TailChainSwapMoveSelector configuration should also support not generating reversing tailchainswaps

          • 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.
          • Open

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: