is nothing stopping your actions from dispatching
>> tasks to a worker thread pool which could then perform the actions
>> concurrently.
>>
>>
>>
>> Thomas
>>
>>
>>
>> *From:* rules-users-boun...@lists.jboss.org [mailto:
>> rules-u
@lists.jboss.org [mailto:
> rules-users-boun...@lists.jboss.org] *On Behalf Of *Tim Jones
> *Sent:* 13 October 2010 07:41
> *To:* Rules Users List
> *Subject:* Re: [rules-users] Parallel processing of large batches of facts
>
>
>
> Interesting suggestions. Couple of questio
a worker thread pool which could then perform the actions concurrently.
Thomas
From: rules-users-boun...@lists.jboss.org
[mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Tim Jones
Sent: 13 October 2010 07:41
To: Rules Users List
Subject: Re: [rules-users] Parallel processing of la
Hi Tim,
I don't believe Drools internals provides multi-threading under "usual"
operation.
If you start to use Timers and Calendars in your rules I have a strong
suspicion that it will; however this is an edge case.
CEP has the benefit of automatically garbage collecting facts that can no
longer
Interesting suggestions. Couple of questions:
Is drools not internally able to multithread a single execution of
fireallrules?
Does CEP offer performance benefits, or is it just a different way of
structuring the problem?
Cheers,
Tim
2010/10/12 Michael Anstis
> Can the aggregation or timesta
Can the aggregation or timestamp range be used to partion your data?
e.g. if you're looking for a data pattern where a fact matches X and Y and Z
can the most course constraint, say X, not be used to partion?
So you may have pre-processing (to partion the data) before hitting other
finer grained
If you have to use a stateful session, with new objects being generated in
RHS code and triggering more rules, then you've had it (since there is no
way to split the 100k facts).
If you don't create new facts in RHS code, you should investigate stateless
sessions. It should be more efficient.
Als
Hello,
I’m working on a project that needs a high performance rules system for
processing batches of objects. Typically I’ll have a dozen or so rules, the
most complex of which will aggregate several objects based on timestamps and
specified data patterns. The objects will come in batches of a f
