Joel,
Just create separate rule files with your rules as you prefer. Then,
at load time, you can use several ways of loading multiple rule files
into the same rulebase. Example:
PackageBuilder.addPackageFromDrl(Reader reader)
Also, if your rules don't change too often and you want save startup
time avoiding compiling then all the time, you can cache (and also
serialize if needed) your compiled rulebase and reuse it. Just be aware
that a serialized rule base is not compatible between versions, so just
a matter of recompiling it when migrating from version to version (what
does not happen too often).
Another performance tip is (if you can) to partition your rules in
smaller rulebases.
[]s
Edson
Joel G. Rivera-González wrote:
yeah...i saw that a while ago...very interesting.
BUT the most important thing is the resources it take from the system
(ie memory) to load 5000 (rough estimate on our rule count) rules with
drools 2.x and with drools 3.x
i think i will do a branch on my clearcase project and will start
working on this.
question..my xml rules are separated in entities, how i do that with DRLs?
Joel G. Rivera-Gonzalez
PRT
"The first 90% of a project takes 90% of the time, the last 10% takes
the other 90% of the time" - Murphy's Law
----- Original Message ----
From: Edson Tirelli <[EMAIL PROTECTED]>
To: user@drools.codehaus.org
Sent: Wednesday, January 3, 2007 5:34:45 PM
Subject: Re: [drools-user] drools load time.
I think someone worked on a XSL to transform 2.x XML files into 3.x
ones, BUT if you do that, you don't get most of the performance benefits
of the new version. The reason is that there is no automatic way to
convert old <java:condition> elements into field constraints... only in
evals().
It requires investments, and it is not always easy/viable for
companies, but the best solution is indeed to convert the XML rules into
the new DRL language.
Have you seen that?
http://markproctor.blogspot.com/2006/11/rush-hour-and-content-based-routing.html
It is a customer case with a performance benchmark between drools 2.5
and 3.0 (3.2 is even faster). It may help to justify such investment...
[]s
Edson
Joel G. Rivera-González wrote:
> you know what...right now i was looking for a way to migrate from 2.x
> rules to 3.0 rules...
> problem is that my system have 2.4 megs of rules in different xml
files...
> i want to give a try to drools 3.0 but i need to know the differences
> between 2.x and 3.x (how to write, load and call the rules)...
> i know that if i mention the performance they will go for it...
>
> any ideas?
>
>
>
> Joel G. Rivera-Gonzalez
> PRT
>
> "The first 90% of a project takes 90% of the time, the last 10% takes
> the other 90% of the time" - Murphy's Law
>
>
> ----- Original Message ----
> From: Edson Tirelli <[EMAIL PROTECTED]>
> To: user@drools.codehaus.org
> Sent: Wednesday, January 3, 2007 5:10:16 PM
> Subject: Re: [drools-user] drools load time.
>
>
> Joel,
>
> Sorry, a long time since I last played with drools 2.x.
> Is it possible for you to migrate to 3.x version? I know it requires
> an effort on rule rewriting, but you got a huge set of benefits in the
> new codebase, from performance to memory consumption, to language
> features, development environment, etc...
>
> []s
> Edson
>
> Joel G. Rivera-González wrote:
>
> > NO one?
> >
> > i just put back the back the old drools libs on the project lib
> > folder...and guess what?
> > loading:
> > before: 1.5 minutes, after: 10s
> > memory:
> > before: 250megs, after:154 megs
> >
> > Joel G. Rivera-Gonzalez
> > PRT
> >
> > "The first 90% of a project takes 90% of the time, the last 10% takes
> > the other 90% of the time" - Murphy's Law
> >
> >
> > ----- Original Message ----
> > From: Joel G. Rivera-González <[EMAIL PROTECTED]>
> > To: user@drools.codehaus.org
> > Sent: Tuesday, January 2, 2007 12:33:14 PM
> > Subject: [drools-user] drools load time.
> >
> > When loading the rules on 2.1 or 2.5 it takes over 1.5 minutes and
> > over 200 megs of memory.
> > a few weeks ago i was compiling with 2.1 but i still had the 2.1 beta
> > 17 (i think)...but after experiencing several problems we delete
> > them. After deleting the beta libs we start having this problem.
> > any ideas?
> >
> >
> > Joel G. Rivera-Gonzalez
> > PRT
> >
> > "The first 90% of a project takes 90% of the time, the last 10% takes
> > the other 90% of the time" - Murphy's Law
> >
>
>
> --
> Edson Tirelli
> Software Engineer - JBoss Rules Core Developer
> Office: +55 11 3124-6000
> Mobile: +55 11 9218-4151
> JBoss, a division of Red Hat @ www.jboss.com <http://www.jboss.com>
<http://www.jboss.com>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3124-6000
Mobile: +55 11 9218-4151
JBoss, a division of Red Hat @ www.jboss.com <http://www.jboss.com>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Edson Tirelli
Software Engineer - JBoss Rules Core Developer
Office: +55 11 3124-6000
Mobile: +55 11 9218-4151
JBoss, a division of Red Hat @ www.jboss.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
