This is because of the Construction Heuristics trying 72 * 600 * 135 combinations for each of the 741 entities.
There's a few ways that could deal with this:
1) Basically, it's this "if (true)" would be false:
https://github.com/kiegroup/optaplanner/blob/master/optaplanner-core/src/main/java/org/optaplanner/core/config/constructionheuristic/placer/QueuedEntityPlacerConfig.java#L86
then it would try 72 + 600 + 135 combinations for each of the 741
entities, which is far more scalable (but reduces solution quality
of the CH).
Unfortunately, that configuration property is not yet exposed in
QueuedEntityPlacerConfig.java
(if it were, it would be a matter of copy pasting the advanced
CH config from the docs and adding that flag).
2) Partitioned Search (use 7.0.0.CR1) heavily speeds up CH's, but
you'll need to write a Partitioner, see the 7.x docs.
With 4 out of 8 cores we've seen a speed up of 30 times for cloud
balancing CH's.
3) Limited selection CH's.
4) Write a custom phase to replace the CH, see *Initializer
classes in examples.
HTH
With kind regards,
Geoffrey De Smet
--
You received this message because you are subscribed to the Google Groups "OptaPlanner development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to optaplanner-d...@googlegroups.com.
To post to this group, send email to optapla...@googlegroups.com.
Visit this group at https://groups.google.com/group/optaplanner-dev.
For more options, visit https://groups.google.com/d/optout.