The loggingLevel (debug) of org.drools.core is high. This decreases performance. Maybe set the loggingLevel to info or lower.
Useful for visualizing the best solver configuration.
Solver | Total | Average | Standard Deviation | Problem |
---|---|---|---|---|
Problem_0 | ||||
Config_0 0 | 0 | 0 | 0.0E0 | 0 0 |
Useful for visualizing the scalability of each solver configuration.
Useful for visualizing the reliability of each solver configuration.
Maximum subSingle count: 1
The benchmarker did not run multiple subSingles, so there is no distribution and therefore no reliability indication.
Useful for zooming in on the results of the best score summary.
Solver | Total | Average | Problem |
---|---|---|---|
Problem_0 | |||
Config_0 0 | 0 | 0 | 0 0 |
Useful for visualizing the return on investment (ROI) to decision makers.
Solver | Average | Problem |
---|---|---|
Problem_0 | ||
Config_0 0 | 0.00% | 0.00% 0 |
Useful for comparing different score calculators and/or score rule implementations (presuming that the solver configurations do not differ otherwise). Also useful to measure the scalability cost of an extra constraint.
Solver | Average | Problem |
---|---|---|
Problem_0 | ||
Problem scale | 6 | 6 |
Config_0 0 | 3,800/s | 3,800/s |
Useful for comparing different score calculators and/or score rule implementations (presuming that the solver configurations do not differ otherwise). Also useful to measure the scalability cost of an extra constraint.
Solver | Average | Problem |
---|---|---|
Problem_0 | ||
Config_0 0 | 0.00% | 0.00% |
Useful for visualizing the performance of construction heuristics (presuming that no other solver phases are configured).
Solver | Average | Problem |
---|---|---|
Problem_0 | ||
Problem scale | 6 | 6 |
Config_0 0 | 5 | 5 |
Useful for extrapolating the scalability of construction heuristics (presuming that no other solver phases are configured).
Useful for visualizing trade-off between the best score versus the time spent for construction heuristics (presuming that no other solver phases are configured).
Entity count: 3
Variable count: 3
Maximum value count: 2
Problem scale: 6
Memory usage after loading the inputSolution (before creating the Solver): 5,545,888 bytes on average.
<solver> <solutionClass>org.optaplanner.core.impl.testdata.domain.TestdataSolution</solutionClass> <entityClass>org.optaplanner.core.impl.testdata.domain.TestdataEntity</entityClass> <scoreDirectorFactory> <easyScoreCalculatorClass>org.optaplanner.core.impl.score.DummySimpleScoreEasyScoreCalculator</easyScoreCalculatorClass> </scoreDirectorFactory> <constructionHeuristic/> <localSearch> <termination> <stepCountLimit>10</stepCountLimit> </termination> </localSearch> </solver>
Name | 2018-09-26_123143 |
---|---|
Aggregation | false |
Failure count | 0 |
Starting timestamp | Sep 26, 2018 12:31:43 PM |
Warm up time spent | 30 ms |
Parallel benchmark count / available processors | 1 / 8 |
Benchmark time spent | 175 ms |
Environment mode | REPRODUCIBLE |
Logging level org.optaplanner.core | debug |
Logging level org.drools.core | debug |
Solver ranking class | TotalScoreSolverRankingComparator |
VM max memory (as in -Xmx but lower) | 954,728,448 bytes |
OptaPlanner version | 7.12.0-SNAPSHOT |
Java version | Java 1.8.0_152 (Oracle Corporation) |
Java VM | Java Java HotSpot(TM) 64-Bit Server VM 25.152-b16 (Oracle Corporation) |
Operating system | Linux amd64 4.18.7-100.fc27.x86_64 |
Report locale | en_US |
Report timezone | Europe/Madrid |