As far as i've read in the documentation, creating statefulKnowledgeSession's is cheap, even though reading the rulebase is not. And you can even persist your sessions in database, so i'd say that's not too much to worry about But i'm a newbie, more experienced users may disagree. _ miguel On Wed, Mar 31, 2010 at 1:59 PM, alim <audrey.lim(a)it-vision.com&gt; wrote: > > Hi everyone, > > I'm trying to find a solution to the following situation: > > - KnowledgeBase with approx. 1000 rules > - Approx. 200 users (hence 200 simultaneous sessions) whereas each session > might most likely have different values for the working memory facts > > So let's say we create a KnowledgeBase (with those 1000 rules) and out of > this one KnowledgeBase we create for each existing session its own > StatefulKnowledgeSession. > Now, how expensive (memory-wise) are these StatefulKnowledgeSessions? Is > it > reasonable to have more than just a few StatefulKnowledgeSessions? > Or is there an other, better approach? > > Thank you very much! > -- > View this message in context: > http://n3.nabble.com/StatefulKnowledgeSessions-tp688305p688305.html > Sent from the Drools - User mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users > -- "To understand what is recursion you must first understand recursion" _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi everyone, I'm trying to find a solution to the following situation: - KnowledgeBase with approx. 1000 rules - Approx. 200 users (hence 200 simultaneous sessions) whereas each session might most likely have different values for the working memory facts So let's say we create a KnowledgeBase (with those 1000 rules) and out of this one KnowledgeBase we create for each existing session its own StatefulKnowledgeSession. Now, how expensive (memory-wise) are these StatefulKnowledgeSessions? Is it reasonable to have more than just a few StatefulKnowledgeSessions? Or is there an other, better approach? Thank you very much! -- View this message in context: http://n3.nabble.com/StatefulKnowledgeSessions-tp688305p688305.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Hi everyone, I'm trying to find a solution to the following situation: - KnowledgeBase with approx. 1000 rules - Approx. 200 users (hence 200 simultaneous sessions) whereas each session might most likely have different values for the working memory facts So let's say we create a KnowledgeBase (with those 1000 rules) and out of this one KnowledgeBase we create for each existing session its own StatefulKnowledgeSession. Now, how expensive (memory-wise) are these StatefulKnowledgeSessions? Is it reasonable to have more than just a few StatefulKnowledgeSessions? Or is there an other, better approach? Thank you very much! -- View this message in context: http://n3.nabble.com/StatefulKnowledgeSessions-tp688305p688305.html Sent from the Drools - User mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users