[JBoss JIRA] (DROOLS-3003) Enhance performance of PMML using decision trees
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3003?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3003:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> Enhance performance of PMML using decision trees
> ------------------------------------------------
>
> Key: DROOLS-3003
> URL: https://issues.jboss.org/browse/DROOLS-3003
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
>
> Refactor the generation of rules and classes by the PMMLCompiler, for PMML resources containing Tree models.
> # Replace any remaining instances of types declared in rules files with POJOs
> # Reduce and/or remove the usage of rules in the process of generating rules and classes
> # Expose/make available the POJO that is generated from the MiningSchema, so that it can be used as input, instead of PMMLRequestData type
> # Update rules to make direct use of the input POJO
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3002) Enhance performance of PMML using scorecards
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3002?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3002:
-----------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44 (was: 2018 Week 39-41)
> Enhance performance of PMML using scorecards
> --------------------------------------------
>
> Key: DROOLS-3002
> URL: https://issues.jboss.org/browse/DROOLS-3002
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Lance Leverich
> Priority: Major
> Labels: drools-core
>
> Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model.
> # Make further usage of POJOs to replace any types declared within the rule file
> # Make the generation of rules and classes be more direct (i.e. reduce/remove the rules engine use in generating rules and classes)
> # Reduce the rules generated so that the number of steps required to apply a model is minimized
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1372) Each call to KieContainer.updateToVersion(ReleaseId version) creates a new classloader for unmodifed rules in the KieModule
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-1372?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-1372:
----------------------------------
Story Points: 5
> Each call to KieContainer.updateToVersion(ReleaseId version) creates a new classloader for unmodifed rules in the KieModule
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1372
> URL: https://issues.jboss.org/browse/DROOLS-1372
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: Bill Tuminaro
> Assignee: Mario Fusco
> Priority: Major
> Attachments: UpdateToVersionCreatingNewClassloaders.java, drools-1372_one.PNG, drools-1372_two.PNG
>
>
> I have attached a reproducer named UpdateToVersionCreatingNewClassloaders.java that creates a KieContainer with a KieModule that contains a single rule (rule name 1081) and then runs a loop that adds 1 rule and removes 1 rule and calls KieContainer.updateToVersion(). Along the way it creates .dmp files.
> If you examine the .dmp files name updrule#_3.dmp (i.e. updrule1_3.dmp , updrule3_3.dmp ) you will see that the number of classloaders for the rule named org.drools.compiler.integrationTests.Rule_10810DefaultConsequenceInvoker increases by 1 each iteration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-1362) accumulate and over window:time usage will stuck drools for a while (from minutes to hours according to number of facts)
by Tibor Zimányi (Jira)
[ https://issues.jboss.org/browse/DROOLS-1362?page=com.atlassian.jira.plugi... ]
Tibor Zimányi updated DROOLS-1362:
----------------------------------
Story Points: 5
> accumulate and over window:time usage will stuck drools for a while (from minutes to hours according to number of facts)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1362
> URL: https://issues.jboss.org/browse/DROOLS-1362
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.5.0.Final
> Reporter: Ertugrul Akbas
> Assignee: Mario Fusco
> Priority: Major
> Attachments: Droolslog.zip
>
>
> We are testing a simple rule. The rule is:
> import com.anet.correlation.*;
> import java.util.*;
> import com.anet.ntLog.collector.*;
> import com.anet.alarm.*;
> import com.anet.util.*;
> import com.anet.correlation.operators.*;
> import com.anet.correlation.utils.*;
> declare EPSObject
> @role(event)
>
> end
> rule "test"
> when
> Number( ) from accumulate(
> generalcorrelationobject1:EPSObject(name=='ert', $temp :avg_snmptrapeps) over window:time( 3m ),
> average( $temp ) )
> then
> end
> we are inserting facts continuously and after 3 minutes - the time which is given as "over window:time( 3m )" -
> drools stuck and then after minutes , starts to conitinue.
> Not: When we test with "over window:time( 30m )" stuck 30 minutes later or When we test with "over window:time( 10m )" stuck 10 minutes later
> Any comment?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months