<br> Yuri,<br><br> Not is a simple and cheap CE to use. In a simple analysis, the cost of NOT CE is even lower than a JOIN, since it will try joins, but will propagate a single tuple. So, go ahead, your second approach is the best way to go.
<br><br> []s<br> Edson<br> <br><br><div><span class="gmail_quote">2007/7/23, Yuri de Wit <<a href="mailto:ydewit@gmail.com">ydewit@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am working on a drools application with few rules and large number<br>of facts. In my first design I tried to avoid excessive joins thinking<br>I was helping improve performance but didnt realized that I was<br>actually shooting myself in the foot. I was basically creating a
<br>single facade-fact that would contain two or three diff concerns<br>joined under the same interface. The problem I am seeing is that for<br>simple things like changing the status of one of many facts would<br>cause that fact to be reevaluated against all the other facts.
<br><br>I then realized that thinking relationally about the problem would not<br>only simplify my solution but also probably make a lot faster.<br>However, in this new and relational solution I will need to make use<br>of many "not" CE.
<br><br>My question is: is there any cost in using "not"s that I should be<br>awae of? Any other words of wisdom re: improving the performance in<br>small rules x many facts?<br><br>thanks,<br>-- yuri<br>_______________________________________________
<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br> Edson Tirelli<br> Software Engineer - JBoss Rules Core Developer<br> Office: +55 11 3529-6000<br> Mobile: +55 11 9287-5646<br> JBoss, a division of Red Hat @
<a href="http://www.jboss.com">www.jboss.com</a>