You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Mark Lybarger <Ma...@CBC-Companies.com> on 2004/05/21 17:54:30 UTC
RE: OutOfMemory after reloads - Performance improvements
> -----Original Message-----
> From: Jeffery Painter [mailto:painter@kiasoft.com]
> Sent: Friday, May 21, 2004 10:54 AM
> To: Turbine Users List
> Subject: Re: OutOfMemory after reloads
>
>
>
> what do you mean by reloaded many times? do you mean starting
> and stopping
> the container? do you mean user's logging in and out?
>
> are you still using turbine 2.1? It isn't fun, but it is
> worth updating to
> the later versions of Turbine. I saw significant performance gains in
> going from 2.1 to 2.2, and 2.3 seems even better.
Could you give a little more info on the performance gains by upgrading turbine? What changes to turbine itself would provide performance enhancements? What scale of improvements did you notice?
I'm highly in favor of getting our turbine current, but it would be much easier to get it done if there were a a tangable benefit (performance improvement).
>
> I've been running a large application on 2.2_01 with a few
> thousand users and not experienced any memory trouble.
> We are running the application in Jetty and not Tomcat though.
Our testing (using imperix?) shows that we'll be having troubles getting much past 50 users. That's just logging in and browsing the web site (not much activity w/ our beans) We're using wls with separate web and app servers (turbine talks to sls ejbs).
>
> when I did get OutOfMemory exceptions, it was most definitely
> trouble with
> my programming and not Turbine's
>
>
>
> On Fri, 21 May 2004, Folkens, Brad wrote:
>
> > Since turbine 2.1 I've noticed a recurring issue with a
> > java.lang.OutOfMemory situation after the turbine framework has been
> > reloaded several times.
> >
> > Has anyone experienced this problem? If so, has there been
> any insight?
> >
> > Bradford A. Folkens
> > bfolkens@downers.us
> >
>
>
> --
> Regards,
>
>
>
> Jeffery Painter
> President
> Kiasoft, Inc. (910) 254-9383 ext 129
>
>
>
> - --
> painter@kiasoft.com http://kiasoft.com
> PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
>
>
> iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U
> YNXabx7DZOV2Hd9LwSTmGpY=
> =dWiu
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: OutOfMemory after reloads - Performance improvements
Posted by Jeffery Painter <pa...@kiasoft.com>.
On Fri, 21 May 2004, Mark Lybarger wrote:
> > -----Original Message-----
> > From: Jeffery Painter [mailto:painter@kiasoft.com]
> > Sent: Friday, May 21, 2004 10:54 AM
> > To: Turbine Users List
> > Subject: Re: OutOfMemory after reloads
> >
> >
> >
> > what do you mean by reloaded many times? do you mean starting
> > and stopping
> > the container? do you mean user's logging in and out?
> >
> > are you still using turbine 2.1? It isn't fun, but it is
> > worth updating to
> > the later versions of Turbine. I saw significant performance gains in
> > going from 2.1 to 2.2, and 2.3 seems even better.
>
> Could you give a little more info on the performance gains by upgrading turbine? What changes to turbine itself would provide performance enhancements? What scale of improvements did you notice?
>
> I'm highly in favor of getting our turbine current, but it would be much easier to get it done if there were a a tangable benefit (performance improvement).
>
I have to say it is really just from what my users are telling me.
At the time we updated to Turbine 2.2 from 2.1 performance did "seem"
to improve significantly. I don't have any hard facts to back this up.
I know there were plenty of bug fixes from 2.1 to 2.2 and moving from 2.1
to 2.2 was a bigger pain than moving from 2.2 to 2.3
Still putting off changing my old app code over to 2.3, but I have
building all my newer apps on 2.3 and it seems better as well.
We also switched to using the blackdown java compiler which sped up build
time and then made the switch from Tomcat to Jetty which was the single
biggest performance boost we achieved.
We now support over 25 users who are in the main order entry system all
day long and several thousand outside users who access limited parts
with simple forms with no trouble at all.
the blackdown jdk decreased build time on our application from around 50
seconds on a clean build with sun's jdk to 13 seconds with blackdown.
my turbine app currently has about 575 class files
Jeff Painter
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org