OK, just a brief update on what I've done and what it taught me.
I created a 'Counter' mbean to track singleton performance counters and
a CounterInterceptor to stick into interceptor stacks to allow me to get
a feel for where the time was going. This told me that the TxInterceptor
was taking
ill chnage things.
-Original Message-
From: marc fleury
To: marc fleury; danch; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: 3/31/01 10:23 PM
Subject: RE: [JBoss-dev] Performance (was Re: [JBoss-user] JBoss verses
Orion)
And who after this will have the guts to argue that we don't n
EMAIL PROTECTED]
|Subject: RE: [JBoss-dev] Performance (was Re: [JBoss-user] JBoss verses
|Orion)
|
|
||I've spent the day running some test similiar to Paul's.
||
||My environment is Linux on a PIII 500, running Sun's 1.3 and
||1.3.1beta JDKs.
||
||In the case of a standalone client lo
|I've spent the day running some test similiar to Paul's.
|
|My environment is Linux on a PIII 500, running Sun's 1.3 and
|1.3.1beta JDKs.
|
|In the case of a standalone client looping and repeatedly calling the
|same method on a stateless session bean, I found that Orion averaged
|about 3ms. per
I've spent the day running some test similiar to Paul's.
My environment is Linux on a PIII 500, running Sun's 1.3 and 1.3.1beta JDKs.
In the case of a standalone client looping and repeatedly calling the
same method on a stateless session bean, I found that Orion averaged
about 3ms. per invoca
