7.3. 更改 OptaPlanner solver 日志记录级别

您可以更改 OptaPlanner solver 中的日志级别，以检查解决者活动。以下列表描述了不同的日志记录级别：

错误：日志错误，除了作为 RuntimeException 丢弃给调用代码的除外。
如果发生错误，OptaPlanner 通常会失败。它抛出子类 RuntimeException，其中包含调用代码的详细消息。为避免重复日志消息，它不会将其记录为错误。除非调用代码明确捕获并消除了 RuntimeException，否则 Thread's 默认"ExceptionHandler" 会将它记录为任何错误。同时，代码会造成进一步危害或模糊处理错误。
警告：日志可疑情况
info ：记录每个阶段和 solver 本身
debug ：记录每个阶段的每个步骤
trace ：记录每个阶段的每个步骤的每个移动

注意

指定 trace 日志记录会显著降低性能。但是，跟踪 日志记录在开发过程中不可评估，以发现瓶颈。

即使 调试日志记录 在快速步骤算法（如 Late Acceptance 和 Simated Annealing）上可能会降低性能，但不适用于 Tabu Search 等较慢的步骤算法。

trace 的和 debug 日志都会导致在多线程中通过大多数附加器进行阻塞。

在 Eclipse 中，对控制台的调试日志往往会导致导致分数计算速度超过 10000 每秒的拥塞。IntelliJ 或 Maven 命令行都不受此问题的影响。

流程

将日志记录级别设置为 debug 日志记录，以查看阶段何时结束以及执行快速的步骤。

以下示例显示了 debug 日志的输出：

INFO  Solving started: time spent (3), best score (-4init/0), random (JDK with seed 0).
DEBUG     CH step (0), time spent (5), score (-3init/0), selected move count (1), picked move (Queen-2 {null -> Row-0}).
DEBUG     CH step (1), time spent (7), score (-2init/0), selected move count (3), picked move (Queen-1 {null -> Row-2}).
DEBUG     CH step (2), time spent (10), score (-1init/0), selected move count (4), picked move (Queen-3 {null -> Row-3}).
DEBUG     CH step (3), time spent (12), score (-1), selected move count (4), picked move (Queen-0 {null -> Row-1}).
INFO  Construction Heuristic phase (0) ended: time spent (12), best score (-1), score calculation speed (9000/sec), step total (4).
DEBUG     LS step (0), time spent (19), score (-1),     best score (-1), accepted/selected move count (12/12), picked move (Queen-1 {Row-2 -> Row-3}).
DEBUG     LS step (1), time spent (24), score (0), new best score (0), accepted/selected move count (9/12), picked move (Queen-3 {Row-3 -> Row-2}).
INFO  Local Search phase (1) ended: time spent (24), best score (0), score calculation speed (4000/sec), step total (2).
INFO  Solving ended: time spent (24), best score (0), score calculation speed (7000/sec), phase total (2), environment mode (REPRODUCIBLE).

INFO  Solving started: time spent (3), best score (-4init/0), random (JDK with seed 0).
DEBUG     CH step (0), time spent (5), score (-3init/0), selected move count (1), picked move (Queen-2 {null -> Row-0}).
DEBUG     CH step (1), time spent (7), score (-2init/0), selected move count (3), picked move (Queen-1 {null -> Row-2}).
DEBUG     CH step (2), time spent (10), score (-1init/0), selected move count (4), picked move (Queen-3 {null -> Row-3}).
DEBUG     CH step (3), time spent (12), score (-1), selected move count (4), picked move (Queen-0 {null -> Row-1}).
INFO  Construction Heuristic phase (0) ended: time spent (12), best score (-1), score calculation speed (9000/sec), step total (4).
DEBUG     LS step (0), time spent (19), score (-1),     best score (-1), accepted/selected move count (12/12), picked move (Queen-1 {Row-2 -> Row-3}).
DEBUG     LS step (1), time spent (24), score (0), new best score (0), accepted/selected move count (9/12), picked move (Queen-3 {Row-3 -> Row-2}).
INFO  Local Search phase (1) ended: time spent (24), best score (0), score calculation speed (4000/sec), step total (2).
INFO  Solving ended: time spent (24), best score (0), score calculation speed (7000/sec), phase total (2), environment mode (REPRODUCIBLE).

Copy to Clipboard

Toggle word wrap

所有花费的时间都以毫秒为单位。

所有信息都记录到 SLF4J，它是一个简单的日志记录传真，它将每个日志消息委派给 Logback、Apache Commons Logging、Log4j 或 java.util.logging。向您选择的日志记录框架添加依赖项。

返回顶部

7.3. 更改 OptaPlanner solver 日志记录级别

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links