You have to distinguish between the time required for building the
KnowledgeBase from the decision table, and the time required for
processing a fact with the 50,000 rules.
If the former is the problem, serializing the KnowledgeBase is the best
you can do, and you don't need Hibernate.
If the latter is the problem, it could be that you are on the wrong
track with the decision table approach. (Is this the long list of 4
values to be compared with 4 fact fields, to obtain a function result
defined by the 5th value?)
On 15/06/2012, zeeshan <zeeshan.spring(a)gmail.com> wrote:
Hi Mike and thanks for replying !
Actually I am planning to store rules in database because calling from
sheet effects performance drastically. So kindly guide me to migrate excel
sheet rules to database using Hibernate or please suggest me other possible
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list