*As a rule of thumb, I would say, cache knowledge bases, but throw away
sessions. Session creation is meant to be fast.
I'm talking about stateless session here :)
On Wed, Oct 27, 2010 at 5:11 PM, Leonardo Gomes
<leonardo.f.gomes(a)gmail.com>wrote:
I might be wrong, but I believe the optimization he's talking
about is the
sequential mode.
Coming back to the original problem in this thread, I'm amazed that you
have 30% of your time linked to the newStatelessSession for a cached
KnowledgeBase! Loading of classes as the explanation for this also sounds
weird... do you spend a lot of time with not using any session so that the
classes get unloaded?
As a rule of thumb, I would say, cache knowledge bases, but throw away
sessions. Session creation is meant to be fast.
Leo.
On Wed, Oct 27, 2010 at 3:00 PM, Bruno Freudensprung <
bruno.freudensprung(a)temis.com> wrote:
>
> You are right; so far (still haven't finished reading the book) it is
> unclear whether the stateless session really implements some kind of
> optimization.
>
> Bruno.
>
> Wolfgang Laun a écrit :
> > Ha!
> > I've been trying to find out about exactly this reputed distinction
> between
> > stateful and stateless sessions, NOT to be confused with "sequential
> mode",
> > which does introduce optimizations.
> >
> > No success so far.
> >
> > -W
> >
> >
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>