-
Feature Request
-
Resolution: Unresolved
-
Minor
-
None
If you configure something like this:
<inheritedSolverBenchmark> ... <solver> ... <localSearch> <selector> <selector> <moveFactoryClass>org.drools.planner.examples.cloudbalancing.solver.move.factory.CloudComputerChangeMoveFactory</moveFactoryClass> </selector> <selector> <moveFactoryClass>org.drools.planner.examples.cloudbalancing.solver.move.factory.CloudProcessSwapMoveFactory</moveFactoryClass> </selector> </selector> <forager> <minimalAcceptedSelection>4</minimalAcceptedSelection> </forager> </localSearch> </solver> </inheritedSolverBenchmark> <solverBenchmark> <name>simulatedAnnealing400</name> <solver> <localSearch> <acceptor> <simulatedAnnealingStartingTemperature>0hard/400soft</simulatedAnnealingStartingTemperature> </acceptor> </localSearch> </solver> </solverBenchmark> <solverBenchmark> <name>simulatedAnnealing800</name> <solver> <localSearch> <acceptor> <simulatedAnnealingStartingTemperature>0hard/800soft</simulatedAnnealingStartingTemperature> </acceptor> </localSearch> </solver> </solverBenchmark>
You get 2 localSearch phases per benchmark, (the second of which crashes due to missing config), instead of 1 localSearch phase as you'd expect.
- relates to
-
PLANNER-68 Benchmarker: Ability to configure a matrix of benchmarks easily
- Resolved