On 19 October 2010 15:02, ravibhatt <ravi(a)qubitdigital.com> wrote:
Thomas,
For testing purposes, i am inserting only 5 rules, 2 ProcessResult Objects
and 20000 ProcessData Objects.
With two ProcessResult objects, this
$processResult1:ProcessResult( inputSource == "table1",... )
$processResult2:ProcessResult( inputSource == "table2",... )
produces a single pair of facts but
$processResult1:ProcessResult( inputSource == $rule.inputSource )
$processResult2:ProcessResult( inputSource != $processResult1.inputSource )
produces two pairs.
Then, associating ProcessData objects with both pairs creates many
more activations.
ProcessResult should contain an attribute which permits you to produce
a single pair,
e.g.
ProcessResult( $id1 : id,... )
ProcessResult( id > $id1,...)
Make sure to eliminate redundant constraints.
-W
When i use a rule that does not use hardcoded "table1", it
inserts first
10000 ProcessData objects fairly quickly, for next 10000 it is taking
forever. Like in 30 mins its able to insert say 1000 or so objects. :-(
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Strange-Performance-P...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users