-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
Currently timeGradient's are always calculated.
And constraintMatches are always disabled in Solver's ScoreDirectory (unless assertion mode is on).
Not all algorithms need timeGradient (in fact only Simulated Annealing needs it currently).
Some unwritten algorithms need constraintMatches, most notably Guided Local Search.
When the Solver starts, it needs to be able to check which features needs to be enabled, by gathering feature Demand (or Request?) instances from it's algorithms. All features which aren't needed are disabled, for performance reasons.
- is blocked by
-
PLANNER-246 ScoreDirector's constraintMatchEnabled should be false when possible: performance speedup for DRL based score calculation
- Resolved
- is incorporated by
-
PLANNER-304 Make OptaPlanner even faster (less slow) and even more scalable
- Resolved