Hi, Robert,

 

I am very interested in the database access part, because I am also considering to add the database access code into my rule. But my current concern is the performance.

 

It would be very appreciated if can let me know how many times of database access is in your whole test suite, which cost 6 seconds? Is it always validating the same user or randomly picking different users to validate --  if using the same query, database may get result cached which will result a better performance? Did you add any arbitrary object caching in your java code for performance optimization?

 

Thanks in advance,

Yang

 

On 8/24/07, Robert Crawford <crawford@kloognome.com> wrote:

Our users are asking to be able to specify custom validations in our
application. I've been undecided whether to use a rules engine or write
our own dynamic validation code.

While it's admittedly still in the "toy problem" stage, I tried using
drools in place of some existing hand-coded validation. The drools version
took the SAME amount of time.

Then I added another rule, to simulate the types of validations our users
want to add, and re-ran.

Again, SAME time.

Admittedly, database access was the big time consumer -- average of 6
seconds per unit of work, and about 15 units of work per test -- but it
was the same for both the rules-based and hand-coded validations.

Excellent work, everyone! You've made my life much, much simpler!



_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users