5:12 a.m.
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Mark Proctor
Priority: Critical
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down
completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId,
eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:55 p.m.
New subject: [JBoss JIRA] Commented: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
[
https://issues.jboss.org/browse/JBRULES-2982?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-2982:
-------------------------------------------
In examination I see a factor 2.13 between drools-compiler 5.1.1 and 5.2.0.CR1 (actually
the offending change was from M1 to M2).
In nurse rostering it's a factor 1.3
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Mark Proctor
Priority: Critical
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down
completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId,
eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [JBoss JIRA] Assigned: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
[
https://issues.jboss.org/browse/JBRULES-2982?page=com.atlassian.jira.plug...
]
Edson Tirelli reassigned JBRULES-2982:
--------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Edson Tirelli
Priority: Critical
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down
completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId,
eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:01 p.m.
New subject: [JBoss JIRA] Closed: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
[
https://issues.jboss.org/browse/JBRULES-2982?page=com.atlassian.jira.plug...
]
Edson Tirelli closed JBRULES-2982.
----------------------------------
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Edson Tirelli
Priority: Critical
Fix For: 5.2.0.CR1
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down
completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId,
eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:01 p.m.
New subject: [JBoss JIRA] Resolved: (JBRULES-2982) Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
[
https://issues.jboss.org/browse/JBRULES-2982?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-2982.
------------------------------------
Fix Version/s: 5.2.0.CR1
Resolution: Done
Thanks for reporting.
The problem was that the new parser was generating a slightly different Descr AST for the
accumulate statement, which in turn was forcing the ReteOO builder to create subnetworks
for all accumulate nodes, even when it would not be necessary, causing the performance
regression.
Fixed. Let us know if you still see a problem, but perf should be roughly equivalent now.
Massive performance degradation from 5.2.0.M1 to 5.2.0.M2
---------------------------------------------------------
Key: JBRULES-2982
URL: https://issues.jboss.org/browse/JBRULES-2982
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (expert)
Affects Versions: 5.2.0.M2
Reporter: Roman Novak
Assignee: Edson Tirelli
Priority: Critical
Fix For: 5.2.0.CR1
the drools-planner SolutionInitializer takes 75 minutes to complete im 5.2.0.M2
5.2.0.M1 took 9,5 Minutes
It also seems that accumulation queries with init, action, result sections break down
completely in performance.
The following query takes now 3 minutes 45 secs to complete. Before it was ~1 sec.
The cardinalities:
PostingPeriodOpt = 5
MediumLocationOpt = 25000
MediumBookingOpt = 13000
query "queryMediumPartlyTaken"
$pp : PostingPeriodOpt()
$mlo : MediumLocationOpt(mTypeId == $pp.mTypeId)
$mp: MediumPeriodUsage( subOptimal > 0 ) from accumulate(
$mbo : MediumBookingOpt ( mediId == $mlo.mediId,
eval(timeInterval.overlaps($pp.getCycle())) ),
init ( MediumPeriodUsage $mpu = new MediumPeriodUsage($mlo, $pp); ),
action( $mpu.addBooking( $mbo.getIndexRange() ); ),
result( $mpu )
)
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4760
days inactive
4775
days old
4 comments
3 participants
participants (3)
-
Edson Tirelli (JIRA) -
Geoffrey De Smet (JIRA)
-
Roman Novak (JIRA)