What does your notion of "response time" include? E.g., loading of a rule base from a package, creating a session from a loaded rule base, inserting N facts,...?
Using decision tables tends to create a large number of simple rules, and this may not be the best way to go. Describe the usage scenario, outline the rules resulting from the decision table(s) (do you have one or several), etc. -W On 23/11/2012, manohars <[email protected]> wrote: > Hello, > > We are using Drools 5.3.0 Final distribution using decision tables(.pkg rule > files) in our solution. However, Drools is taking a lot of memory (@ 350 mb > on Linux-64bit). > On profiling,we realize that huge number of short lived objects are getting > created.(org.drools.impl.StatefulKnowledgeSessionImpl, IndexVariableResolver > class and org.mvel2.* classes). It leads increase in Garbage Collection > cycles there by leaving an impact on average response time. > Is there any clever way to use Drools to achieve @ 1 millisecond to 2 > millisecond response time given the rules are simple? We tried to use drl > based rules but no improvement. > Any idea about how to deal with this such a big memory contributors ? > > Regards, > Manohar > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Drools-consuming-a-lot-of-memory-for-short-lived-objects-thus-impacting-average-response-time-tp4020948.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users > _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
