m:* rules-users-boun...@lists.jboss.org [mailto:
> rules-users-boun...@lists.jboss.org] *On Behalf Of *Leonardo Gomes
> *Sent:* Wednesday, April 27, 2011 12:10 PM
> *To:* Rules Users List
> *Subject:* Re: [rules-users] Memory issue with drools (using 1 rules)
>
>
>
>
>
ules-users-boun...@lists.jboss.org] On Behalf Of Leonardo Gomes
Sent: Wednesday, April 27, 2011 12:10 PM
To: Rules Users List
Subject: Re: [rules-users] Memory issue with drools (using 1 rules)
http://drools.46999.n3.nabble.com/maven-drools-plugin-to-compile-DRL-s-at-build-time-td725751.html
2011/4/27 G
http://drools.46999.n3.nabble.com/maven-drools-plugin-to-compile-DRL-s-at-build-time-td725751.html
2011/4/27 Geoffrey De Smet
> there's a maven-drools-plugin out there in the wild to precompile your
> rules.
>
> Op 27-04-11 04:27, Edson Tirelli schreef:
>
>
> Besides all suggestions already
there's a maven-drools-plugin out there in the wild to precompile your
rules.
Op 27-04-11 04:27, Edson Tirelli schreef:
Besides all suggestions already made in other e-mails, it is also
worth considering if you can pre-compile rules and just load them at
runtime instead of compiling them
Would removing the eval() from your rule reduce memory usage?
Jevon
2011/4/26 Shebs, Liron
> Hello All,
>
>
>
> I’m working at HP Software R&D and we are considering using drools in our
> product.
>
> Benchmarking tests showed that running 10,000 rules consumes 382mb.
>
> This is too high for o
Besides all suggestions already made in other e-mails, it is also worth
considering if you can pre-compile rules and just load them at runtime
instead of compiling them at runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile y
>
> Benchmarking tests showed that running 10,000 rules consumes 382mb.
Are you talking about the memory footprint of your KnowledgeBase when you
load it or is after the insertion of facts / execution of rules?
Do you have any more detailed profiling information to share with us? We
might be abl
Your eval, you could probably replace by something like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity",
field == "sta
The rule you have shown suggests that many of your rules (if not all)
compare fact fields with literals. If there are groups of rules where just
these literals vary, and the corresponding RHS logic is also uniform (just
varying with the values stored or written or whatever), then you might
consider
is it necessary to execute 1 rules in one time for your case?
Why don't execute rule selectively?
2011/4/26 Mark Proctor
> There is no out of the box way to improve that, beyond just partitioning
> your rulebases yourself.
>
> If you would like to get involved in R&D we can do lazy netwo
There is no out of the box way to improve that, beyond just
partitioning your rulebases yourself.
If you would like to get involved in R&D we can do lazy network
building and try pushing unused parts of the rule network to disk.
Mark
On 26/04/2011 12:05, Sh
Hello All,
I'm working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how we
can improve it.
Technical details:
- Drools vers
12 matches
Mail list logo