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

Improve Partitioned Search logging

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Minor
    • 7.5.0.Final
    • 7.4.1.Final
    • optaplanner-core
    • None
    • 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48
    • NEW
    • NEW

    Description

      15:35:10.356 [OptaPool-4-PartThread-3] TRACE         Move index (8), score (-2init/0), move (M {null -> 8}).
      15:35:10.356 [OptaPool-4-PartThread-2] INFO          Construction Heuristic phase (0) ended: time spent (6), best score (0), score calculation speed (12750/sec), step total (5).
      15:35:10.356 [OptaPool-4-PartThread-1] DEBUG             LS step (1), time spent (6), score (0),     best score (0), accepted/selected move count (1/1), picked move (E {0 -> 5}).
      15:35:10.356 [OptaPool-4-PartThread-3] TRACE         Move index (9), score (-2init/0), move (M {null -> 9}).
      15:35:10.356 [pool-2-thread-1] DEBUG     PS step (1), time spent (6), score (-5init/0), new best score (-5init/0), picked move (org.optaplanner.core.impl.partitionedsearch.scope.PartitionChangeMove@d973e38).
      

      There are several issue with logging when using <partitionedSearch>:

      1. Moves are not indented. They should be step + 1 indentation level.
      2. PartitionChangeMove.toString() is not implemented while it could show some useful info like the index of partition it's coming from.
      3. Partition thread loggers have a longer name which breaks the indentation when compared to log messages from the main thread.

      Attachments

        Activity

          People

            jlocker Jiří Locker
            jlocker Jiří Locker
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: