If you have many, many rules I think an optimisation would be to save a serialised rulebase and use this instead of creating one from your DRL (which would include parsing and RETE matrix generation). This would become a "one off" packaging\deployment action. At runtime you'd deserialise the rulebase. Also have a look at AgendaGroups - they allow you to trigger sub-sets of rules in the rulebase. ________________________________ From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Kunal Shah Sent: 22 March 2007 14:37 To: rules-users(a)lists.jboss.org Subject: [rules-users] Can Jboss rules handle large no. of RuleBases? I am new to JBoss rules and trying to figure out whether we can use it in our application. I have one doubt about its usability in our app after reading documentation. Documentation says that creation of RuleBase is a heavy operation and shouldn't occur many times. But in our app we have thousands of entities each possibly having a separate RuleBase. Is this feasible? Basically rules used by one entity may not be used by other (or should not be used in certain cases). So is there a way of sharing a RuleBase among multiple entities but not sharing all the rules defined in it, e.g. when we create WorkingMemory can you specify to use rules having certain property only like 'namespace' (or package)? I will appreciate any pointers/ideas regarding this. Kunal Shah Development 214-445-2121 972-934-7376 (fax) kshah(a)sensorlogic.com <mailto:kshah@sensorlogic.com> www.sensorlogic.com