[rules-users] pre-load rules and performance

[Wolfgang Laun]

Don't insert the stuff fetched from the DB right away, store them in
a cool, dry place.

When all this pre-load activity is over, take the collection and insert
it in one fell swoop.

-W

On 21/02/2014, ismaximum <mnrz57 at gmail.com> wrote:
> Hi
>
> I am trying to make a big sets of rules more efficient. So we have this drl
> file with lots of rules and the same rule-flow-group. About 15 of them are
> rules we call them pre-load rules and they have a high salience numbers.
> These rules will fetch data from database and insert then into WM.
>
> As I know, each insert makes all the rules get activated... there are lots
> of other objects and facts being added by these so-called pre load rules...
>
>
> *How can we make this efficient? How can I say no rule gets activated
> unless
> all the pre-load ones are done?*
>
> Because these rules are inserting facts into memory (we are validating
> incoming request and need to consider existing data in database) we can't
> put new conditions in other rules to stop them from being fired.
>
> Does anybody have an idea or had such experience with this?
>
> Thanks
>
>
>
>
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/pre-load-rules-and-performance-tp4028216.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>