Guys,
I cannot pinpoint what it is, but is probably something interacting with the
embedded tomcat. Calling the beans from an outside client shows little
difference for the non-optimized version of the bean. 5.8ms (JBoss 2.0
FINAL) vessus 6.1ms (Current CVS), something like that. Way weird, since the
09 snapshot works fine.
Hugo
----- Original Message -----
From: "Ole Husgaard" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Saturday, February 10, 2001 9:48 PM
Subject: Re: [jBoss-Dev] MAJOR SLOWDOWN in jboss' performance in a couple
ofdays...
> Hi,
>
> marc fleury wrote:
> > Ole,
> >
> > Let's not do the finger pointing. I trust you know what you are doing.
>
> Sorry, no finger pointing intended.
> Just trying to point out possible causes
> of this. Also wanted to say that I don't
> think this is due to the JTA changes,
> but that I am NOT sure about it.
>
> Since Hugo narrowed this down to a short
> time interval, finding out what went
> wrong shouldn't be too hard.
> This because we don't have to look at
> the entire source, but only at the few
> things changed that day.
>
>
> > We
> > also need a straighter test harness... so that commits don't result in
> > aberations like this one.
>
> Good idea. Current tests mostly do only
> functionality test, but it should be
> simple to make tests warn if
> performance is a lot worse than one
> would expect.
>
> The jbosstest load test gives almost the
> same results with and without the JTA
> changes.
>
>
> Best Regards,
>
> Ole Husgaard.
>
