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

OrderByMoveIndexBlockingQueue: backlog.clear() isn't synchronized + all the synchronization reduces parallelism

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • optaplanner-core
    • NEW
    • NEW

      OrderByMoveIndexBlockingQueue

      • The backlog.clear() might happen after something is already added in a new step? Maybe it's not possible, but the code isn't really simple to prove that.
      • Do the synchronized blocks reduce horizontal scaling? I am not convinced it does or it doesn't. We need proof.

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

                Created:
                Updated: