Many of the systems use large amounts of data or large numbers of rules by
applying indices inside rules or by processing transactions that could be
batched - which really increases the number of rules or that that are seen.
One of my customers used indices in rules creating rulesets of ~ 200,000
rules. With analysis the number of rules was reduced to ~ 10 + some data
structures. If account processing transactions can be grouped together then
the number of transactions may be dramatically reduced.
The approach of using a thinner client with seperate sessions on seperate
processes using partitioned data is a good idea. If you don't have an
intuititve key then you may want processes to processes chunks of queued
data as processes are ready.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-5-3-partitioned-rule-base-tp3793...
Sent from the Drools: User forum mailing list archive at
Nabble.com.