That's a possibity... it also strikes me that that "fastTM" is gone, like
gone :(
I really believe we need a "realTM" and "fastTM". I suspect fastTM will be
good for many many cases and it's overhead is key.
(btw the 2nd and 3rd spot were for "setContextClassLoader" and
"getContextClassLoader" and there I think that a pool of threads (per
containerInvoker, with preset CL) will help.
But clearly we can do better in the TM
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Juha-P Lindfors
|Sent: Saturday, October 28, 2000 10:00 AM
|To: jBoss Developer
|Subject: RE: [jBoss-Dev] Per-container transaction managers and
|outgoingcalls
|
|
|
|
|On Sat, 28 Oct 2000, marc fleury wrote:
|
|> |We have an old (currently very minor) problem, that
|> |I would like to see fixed:
|>
|> we have other problems, namely optimizeIt says we spend 40% of
|our time in
|> Tx.begin() :P
|
|Something you could try is pooling the tx and xid implementations in
|capsule. Now one instance is created per begin() and
|capsule.reuse() creates just one xid per call (which goes into stuff like
|System.properties on every call, this might cost you).
|
|Since these are heavily used, might wanna create a bunch of them at once,
|instead one every call.
|
|-- Juha
|
|
|
|
