Edson Tirelli-3 wrote:
>
> Yuri,
>
> Right now, the only way is to work with different rule bases and
> working
> memories. Even using agenda-groups or rule-flow, rules are still being
> eagerly evaluated, as this is how standard Rete works.
> The problem of creating and canceling too many activations is a known
> problem and the only way around it right now is sequential mode, but
> sequential mode has some restrictions on what you can do. For instance,
> you
> must work with a stateless working memory and can not modify/retract facts
> in your rules to work with sequential mode, but it will give you big
> performance boosts.
>
> We are evaluating the possibility of creating physical network
> partitions for next version, but that will require some R&D yet.
>
> []s
> Edson
>
> 2007/8/14, Yuri <
ydewit@gmail.com>:
>>
>> Dr. Gernot Starke <gs <at>
gernotstarke.de> writes:
>> > can you detail your problem a little?
>>
>> I basically need to find perfect matches between two different sets of
>> objects.
>> If perfect matches are not found, I then create bulks of objects that are
>> then
>> used in combination with the individual ones to find bulk matches. If no
>> matches
>> are found I need then to categorize the breaks (around 10 different
>> categorizations) and report them.
>>
>> The matching criteria between two object is specific enough to be fast.
>> Once I
>> get into break, which basically is removing some criteria components, the
>> possible combinations increase exponentially. Bulking just compounds the
>> problem
>> by adding more matchable/breakable facts into memory.
>>
>> My bulking logic (I didnt have collect when I started with 3.0) starts a
>> bulk
>> looking for two diff objects with the same bulkling criteria (this is my
>> first
>> potential cross product since drools would produce C!/N!(C-N)!
>> combinations).
>> Then once the bulk for a given criteria is create I have a second rule
>> that
>> expands or contracts the bulks as new facts are asserted causing many
>> different
>> side effects.
>>
>> What I am basically seeing is that asserting a fact that would for
>> instance be a
>> perfect match, causes many of the bulking and breaking rule activations
>> to
>> be
>> created and then cancelled. Considering that I am talking about tens or
>> hundreds
>> of thousands of facts I thought that if I could stage the activation
>> creations I
>> would increase processing speed.
>>
>> With 15K objects on each side I have been seeing something like 1
>> assertion per
>> second.
>>
>> I am aware that this could be cross product somewhere but I have already
>> revised
>> the rules many many times so now I am looking for other alternatives.
>>
>> I am now trying to understand looking I basically need to find perfect
>> matches
>> between two different sets of objects. If perfect matches are not found,
>> I
>> then
>> create bulks of objects that are then used in combination with the
>> individual
>> one to find bulk matches. If no matches are found I need then to
>> categorize the
>> breaks (around 10 different categorizations) and report them.
>>
>>
>> _______________________________________________
>> rules-users mailing list
>>
rules-users@lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>
>
>
> --
> Edson Tirelli
> Software Engineer - JBoss Rules Core Developer
> Office: +55 11 3529-6000
> Mobile: +55 11 9287-5646
> JBoss, a division of Red Hat @
www.jboss.com
>
> _______________________________________________
> rules-users mailing list
>
rules-users@lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
--