Someone already mentioned writing "good" rules versus "bad" rules
which is
definitely critical - things like avoiding things like eval when possible.
For our stateful rules session we took a lot of time in designing the
architecture, facts, etc to avoid having to do any non-rules processing (db
queries, updates, etc) in our rules session. Stateless rules sessions you
can perhaps get away with a little more inefficiency since each request can
operate in it's own thread independent of other requests. Regardless of
stateless vs stateful you just have to be very conscious of how you write
the LHS of your rules and avoiding time consuming activities in the RHS of
your rules. --
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Drools-Performance-tp286987...
Sent from the Drools: User forum mailing list archive at
Nabble.com.