Hi all!
Can anybody point me to a performance evaluation of Drools? I found some papers
[1], [2] which focus on the rules part but I'm particularly interested in the
event processing part of Drools. I want to know how many events can be
processed per second with which latency, something that
The standard well-established answer to this kind of question is that no
benchmark can provide a reliable basis for predicting the behaviour of any
particular application.
It's easy to benchmark the simple insertion of facts (= events) where there
is no or just a single rule; this will give you
Hello there
I am new to all drools...
How can I 'mutex' in drools? Or could you suggest a better concept for that?
(i mean, when two rules would fire : rule1 and rule2 in agenda
the mutex is checked and : mutex for this case is defined, rule1
= higher, rule2 = lower prio
only the one
Hello itchupe:
I think you mean what in Drools is called SALIENCE.
Look for that rule attribute in..
http://downloads.jboss.com/drools/docs/5.1.1.34858.FINAL/drools-expert/html/ch04.html#d0e3573
Best regards,
Manuel Ortiz.
2011/6/28 itchupe itch...@gmail.com
Hello there
I am new to all
The hairy catchword in the post is only.
Most of the time, it's best to design the conditions so that only one rule
will reach the agenda.
If this is too circumstantial, salience might be used to let the special
case fire before the general case; but then something must be done to
remove the
Of course, in the then part of rule1 you will have to set a fact that
is checked in the when condition in rule2 to ensure that rule2 is not
executed if rule1 has executed.
Chris
On 28/06/2011 12:30, Manuel Ortiz wrote:
Hello itchupe:
I think you mean what in Drools is called SALIENCE.
Look
okay. I am not a big fan of mutex, so best is I redesign it as described.
Thanks very much for your answers!
itchupe
--
View this message in context:
http://drools.46999.n3.nabble.com/MUTEX-mutual-exclusion-in-Drools-tp3117430p3117624.html
Sent from the Drools: User forum mailing list archive
Hello all. I'm at the point where I need to pick the brains of those of you
who have spent significant time with Drools I am just in the process of
trying to decide if Drools is the right choice for a high volume trading
application. It would be best if there were some simple examples out there
Hi list,
I feel this should be an elementary question but unfortunately I haven't
been able to find a solution.
I would like to perform date arithmetic in the when part of a rule.
For example, I would like to express something like:
rule Date compare rule
dialect mvel
when
a : A()
b : B(
See the Fusion manual, section on Temporal Reasoning/Temporal Operators.
Even when the facts aren't events, these operators can still be applied to
fields of type Date, e.g.
$p1: Person( $dob1: dob )
$p2: Person( $dob2: dob after[3d] $dob1 )
-W
On 28 June 2011 18:02,
Hi,
because of https://issues.jboss.org/browse/JBRULES-2942 i just migrated our
(maven) project to 5.2.0.Final - we depend on salience in some of our rules.
However, after the salience issue was gone I'm facing a new problem in several
test cases:
Rules in previously (drools 5.1.1) working
I am working to migrate my project from 5.0 to 5.2.0 Final. I am getting an
error that I cannot figure out how to fix.
I get the error stack trace below my email signature. The only thing the
consequence does is insert an object. This rule worked well in 5.0, and some
of the early
Interesting. I tried to use this syntax to find out if a date is older than
now using this source:
$p2: Person( $dob2: dob before[3d] new Date() )
but I get and exception: org.drools.RuntimeDroolsException: The 'before'
operator can only be used to compare one event to another, and never to
Thanks for the quick reply.
I forgot to mention that I'm using 5.0.1, but I'll look at the Fusion
manual for more info.
-Stathis
Wolfgang Laun wrote:
See the Fusion manual, section on Temporal Reasoning/Temporal Operators.
Even when the facts aren't events, these operators can still be applied
14 matches
Mail list logo