At first start with tuning JVM. Xms, Xmx parameters. How much physical
memory you have? If above 3.xx GB you need 64 bit JVM. If this is not
enough just kick Profiler.
Pavel
2010/3/2 Shah, Malay <Malay.Shah(a)morganstanley.com>:
Hi,
We have an drools 5.0.1 application that uses StatelessSession and high
volume of objects (facts) that we need to apply static rules on, and having
out of memory issues doing so. We added the following three properties as
given in the drools documentation for decreasing the memory usage:
drools.shadowproxy=false
drools.maintainTms=false
drools.sequential=true
As per the following blog, there is an algorithm to minimize the engine
work, and memory usage.
http://blog.athico.com/2007/07/sequential-rete.html
Are the properties above sufficient to trigger this algorithm, or do we need
to do write extra code for this?
Also, does the "drools.sequential" property make sure that rules are applied
sequentially on facts? If so, is there a hook into the drools engine to
figure out which particular rule is consuming more memory or having more
execution time?
Thanks in advance.
Malay Shah
________________________________
NOTICE: If received in error, please destroy, and notify sender. Sender does
not intend to waive confidentiality or privilege. Use of this email is
prohibited when received in error. We may monitor and store emails to the
extent permitted by applicable law.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users