[jboss-jira] [JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

[Geoffrey De Smet (Jira)]

    [ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964134#comment-13964134 ] 

Geoffrey De Smet edited comment on DROOLS-4984 at 2/5/20 7:41 AM:
------------------------------------------------------------------

[~rsynek] Drools has 2 systems: "plain DRL exe mode" (AKA legacy mode) and "exe model exe mode" (AKA new mode).
By default, Drools uses the new mode.
But optaplanner currently changes it to use the legacy mode.
After the 7.7 cut-off, luca will switch it to use the new mode, with this jira.

Radovan, *can QA run a benchmark of optaplanner-examples (almost all use cases at least 1 dataset) to compare performance between the legacy mode and the new mode?*
The flag code is in ScoreDirectorFactoryConfig (do git blame and look for Luca's changes), should be easy to switch.

The performance should be the same, in theory... :)


was (Author: ge0ffrey):
[~rsynek] Drools has 2 systems: "plain DRL exe mode" (AKA legacy mode) and "exe model exe mode" (AKA new mode).
By default, Drools uses the new mode.
But optaplanner currently changes it to use the legacy mode.
After the 7.7 cut-off, luca will switch it to use the new mode, with this jira.

Radovan, *can QA run a benchmark of optaplanner-examples (all use cases at least 1 dataset) to compare performance between the legacy mode and the new mode?*
The flag code is in ScoreDirectorFactoryConfig (do git blame and look for Luca's changes), should be easy to switch.

The performance should be the same, in theory... :)

> Enable the executable model in Optaplanner
> ------------------------------------------
>
>                 Key: DROOLS-4984
>                 URL: https://issues.redhat.com/browse/DROOLS-4984
>             Project: Drools
>          Issue Type: Bug
>          Components: executable model
>            Reporter: Luca Molteni
>            Assignee: Luca Molteni
>            Priority: Major
>
> Currently it's disabled



--
This message was sent by Atlassian Jira
(v7.13.8#713008)