]
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: