It's common Rete wisdom to order patterns by expected frequency of
matches, in descending order.
Does this also apply to constraints within a single pattern? For
example, is it better to write, for a New York address
Address( street == Broadway, number == 1)
than
Address( number == 1,
On 08/04/2010 19:56, Wolfgang Laun wrote:
It's common Rete wisdom to order patterns by expected frequency of
matches, in descending order.
Does this also apply to constraints within a single pattern? For
example, is it better to write, for a New York address
Address( street == Broadway,
To sum it up: it doesn't hurt if you put constraints using == against one out of
a wide range of values up front, and chances are good that it will improve
performance.
On Fri, Apr 9, 2010 at 1:55 AM, Mark Proctor mproc...@codehaus.org wrote:
On 08/04/2010 19:56, Wolfgang Laun wrote:
It's
