so to summarize, the system would have lots of simple rules. In those cases, hashing would definitely improve the performance. In some cases, it could be constant performance regardless of the number of rules if the conditions are string comparison like String.equals(string2).
http://woolfel.blogspot.com/2005/09/more-ideas-on-optimization-today-ive.html http://woolfel.blogspot.com/2005/09/adjustment-to-unique-optimization-last.html I have 2 blog entries on the topic if you're interested in reading more. peter lin On 12/13/05, 王在祥 <[EMAIL PROTECTED]> wrote: > > Yes. the nodeshare example shows it. But It is still low effective and can > be improved more. > > For example, we design a air price rule system, there should be more than > 10K price rules, and for a given fact(a flight), there should be only some > rules matches(eg, 10 rules). if the rules engine need to evaluate each > condition, then the cost maybe very expensive. > >
