5:05 a.m.
We have a set of rules (lets call them old rules) running in our strategy
server.
A new requirement is that - the client can make calls to the server, at that
point new rules need to be loaded in the workin memory (at run time), if the
rules get executed then the rules need to be removed from the WorkinMemory
(after the consequence section is executed)
I would like to know if repeated adding and removing of rules in the working
memory will lead to performance issues?
i.e. when the new rules are added/removed the old-set-of rules will still be
evaluated in the background, will this hamper performance?
--
View this message in context:
http://old.nabble.com/Query-on-performance-when-adding-removing-rules-tp2...
Sent from the drools - user mailing list archive at Nabble.com.
3:57 a.m.
any suggestions regarding the impact on performance???
DeepakA wrote:
We have a set of rules (lets call them old rules) running in our strategy
server.
A new requirement is that - the client can make calls to the server, at
that point new rules need to be loaded in the workin memory (at run time),
if the rules get executed then the rules need to be removed from the
WorkinMemory (after the consequence section is executed)
I would like to know if repeated adding and removing of rules in the
working memory will lead to performance issues?
i.e. when the new rules are added/removed the old-set-of rules will still
be evaluated in the background, will this hamper performance?
--
View this message in context:
http://old.nabble.com/Query-on-performance-when-adding-removing-rules-tp2...
Sent from the drools - user mailing list archive at Nabble.com.
1:09 p.m.
It would perform less well, especially if you're parsing new rules and building new
rulesets with each request. But as with every performance issue, you never know for sure
until you mock up and benchmark.
But, some questions to get more detail:
Do you want the old rules to interact with the new rules? If not, it's best to create
a new rulebase and spawn sessions from that. This is especially the case if you're
doing concurrent requests against the same rulebase and don't want two sessions
sharing their new rules.
Will you reuse new rules, or are they unique with every request that adds them? (i.e.
could a subsequent request use the new rules without having to add them again?)
Can you give more details about the problem domain?
--- On Tue, 11/24/09, DeepakA <angeshwar(a)gmail.com> wrote:
From: DeepakA <angeshwar(a)gmail.com>
Subject: Re: [rules-users] Query on performance when adding/removing rules
To: rules-users(a)lists.jboss.org
Date: Tuesday, November 24, 2009, 3:57 AM
any suggestions regarding the impact on performance???
DeepakA wrote:
>
> We have a set of rules (lets call them old rules)
running in our strategy
> server.
> A new requirement is that - the client can make calls
to the server, at
> that point new rules need to be loaded in the workin
memory (at run time),
> if the rules get executed then the rules need to be
removed from the
> WorkinMemory (after the consequence section is
executed)
>
> I would like to know if repeated adding and removing
of rules in the
> working memory will lead to performance issues?
>
> i.e. when the new rules are added/removed the
old-set-of rules will still
> be evaluated in the background, will this hamper
performance?
>
--
View this message in context:
http://old.nabble.com/Query-on-performance-when-adding-removing-rules-tp2...
Sent from the drools - user mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
5485
days inactive
5486
days old
2 comments
2 participants
participants (2)
-
DeepakA -
Greg Barton