|Yeah, I guess it's cool now that you removed InstancePooling. God, pooling
|just fucked everything up and caused a lot of complexity. I wonder if
|pooling actually had any effect on performance anyways?
we will see... it is one of those things where a fancy CMP engine would
SPEED us up SO MUCH that you could manually invoke the beans by reflection
20 times and still be ok... optimizations where they really are important is
my first rule. Optimize the what takes time, not what is fast, relatively
speaking it is a no brainer.
We saw with rickard that Proxy creation is a bit slow and he mentioned a
flag at the object level to allow pooling... will have to research that...
but for the pools I believe it is non important
|Still, for Stateful beans, you're adding complexity for the time between
|when the Stateful bean gets scheduled for passivation, and when the
|Passivator Thread actually runs. Which is only a few milliseconds, right?
|If the Stateful bean is scheduled for passivation, this usually means that
|it has timed out. It seems with the unscheduledPassivation stuff, what
|you're really doing is just extending the configured timeout
|period. So why
|schedule passivation? Just do it. Am I making any sense here?
yes :)
passivation you don't get rid of (btw I did NOT get rid of the caches with
LRU, working well) it is still the movement out of cache, that you do it in
one thread or the other, you still need to synchronize with what is going on
on stateful. Stateful is the itch, entity as we know is straightforward, it
is the stateful stuff since this is the state. If you don't have that you
really can destroy state in cache (hence the only representation of the
stateful cache). You come you want the state, it is not in cache but not in
disk yet (or any secondary storage) it is *passivating*, you create a new
copy of the stateful bean and you have another copy on disk, booom! fucked
up!
that needs to be synchronized and simone does it in 2 steps... again I
thought that was actually quite all right if not downright elegant with the
entity symetry... (he did do somethings right) I could be wrong, if you
really find that it is not adding much then sure, simple is good. I am ok
with it either way (as long as it all works :)
Let me commit (almost there)
marcf
|
|
|Bill
|
|
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
