That is the most common use case and Drools was designed to work like
that: one or more shared kbases and multiple non-shared sessions. The only
catch is that you need to fine tune what is the ideal rate of sessions/kbase
in your use case, because the creation of a session locks a kbase, but after
a session is created, all operations are concurrent. In some uses cases 200
sessions per kbase is fine, but in some cases the ideal rate could be 10,
100 or 1000 sessions per kbase. You need to check what works best for you.
Edson
2010/3/31 alim <audrey.lim(a)it-vision.com>
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
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @
www.jboss.com