eval is only slower because it does not allow for indexing of data.
I don't believe your use case, which looks at nested data structures,
would allow indexing of data either.
So you'll probably gain in performance from a hard coded java method.
Mark
On 22/07/2012 03:40, lhorton wrote:
do not scoff so quickly, WL. eval() can be a big performance kill,
since
eval() condition is always executed during rule evaluation. For example,
if the eval is on a remote invocation that might hang or be sluggish (long
timeout) it can drag the server down.
--
View this message in context:
http://drools.46999.n3.nabble.com/NESTED-LOOPS-Possible-tp4018811p4018817...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users