On Thu, 22 Mar 2001, Mark Balster wrote:

> If Jasper is generating some inefficient code, would Jikes help?
> 

Not really.  The code generated for your page will still do more stuff
than it needs to ... but it will compile faster :-).

What matters the most is what kinds of optimizations the page compiler
does when generating the Java source for the corresponding servlet --
for example, reusing tag instances intelligently would be of great benefit
to a Struts-based application.

Craig


> ----- Original Message -----
> From: "James Cook" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, March 21, 2001 8:55 AM
> Subject: RE: Performance of struts
> 
> 
> > I find the 240ms delay satisfactory for most of my apps because the
> business
> > side logic usually takes longer to execute.
> >
> > I applaud WebLogic however for their timings. Especially (IIRC) since
> > WebLogic is supposed to be 100% Java. I know that some other servers that
> > churn JSP very well are hybrids. It would be interesting to look at the
> > Jasper-generated source and see where optimizations can be done.
> >
> > jim
> >
> > > -----Original Message-----
> > > From: Jeff Schnitzer [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, March 19, 2001 11:24 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: Performance of struts
> > >
> > >
> > > Struts should suffer the same performance issues as WebWork.  There are
> > > a handful of benchmarks here:
> > >
> > > http://sourceforge.net/docman/display_doc.php?docid=2243&group_id=14797#
> > > Na96
> > >
> > > The relative performance on a tag-heavy benchmark:
> > >
> > > Tomcat 3.2: ~380 milliseconds
> > > JRun 3.0: ~350 milliseconds
> > > Resin 1.2.1: ~250 milliseconds
> > > Orion 1.3.8: ~220 milliseconds
> > > WebLogic Server 6.0: ~140 milliseconds
> > >
> > > Jeff
> > >
> > > >-----Original Message-----
> > > >From: Eric Brown [mailto:[EMAIL PROTECTED]]
> > > >Sent: Monday, March 19, 2001 7:58 PM
> > > >To: '[EMAIL PROTECTED]'
> > > >Subject: RE: Performance of struts
> > > >
> > > >
> > > >I haven't done any comparisons recently, but I think Resin from
> > > >www.caucho.com is very reasonably priced and written specifically with
> > > >performance in mind (from what I can tell). I've written a
> > > >Java based http
> > > >proxy server before and I can tell you that from looking at some of the
> > > >things Resin has done, they know where Java's performance
> > > >bottlenecks are.
> > > >(For example, they translate all socket streams into byte
> > > >arrays instead of
> > > >using strings, etc.) They have some performance comparisons on
> > > >their web
> > > >site.
> > > >
> > > >Others are:
> > > >Orion - Know nothing about
> > > >BEA WebLogic - Very expensive, complex to deploy and
> > > >performance is mediocre
> > > >according to my sources
> > > >ATG Dynamo - Expensive but good for commerce if needed. They
> > > >are focused on
> > > >commerce, so probably not focused on performance.
> > > >Netscape/iPlanet - I've heard the performance is not impressive
> > > >IBM WebSphere - This is an up-and-coming competitor to
> > > >WebLogic and ATG. It
> > > >used to be buggy and is still expensive. Performance is
> > > >unknown, but I would
> > > >favor Resin as it comes with source and is less expensive.
> > > >Jrun - Priced reasonably. Nice integration with other Allaire
> > > >products. No
> > > >special commerce features. I think it has had some
> > > >compatibility problems,
> > > >but it seems a good engine these days. All the same, I don't
> > > >think you can
> > > >get source and I haven't done performance tests.
> > > >Enhydra - This is just Tomcat. They have their own framework
> > > >that is less
> > > >comprehensive than struts called XMLC. Its big advantage is
> > > >that it does a
> > > >better job of separating UI from code.
> > > >
> > > >I think to some degree, it is equally important to look at the
> > > >JVM you are
> > > >running on. Consider looking at the Volano report at
> > > >http://www.volano.com/report.html.
> > > >
> > > >My team is using Tomcat/Forte for development and will use
> > > >Resin/Apache for
> > > >deployment.
> > > >
> > > >Eric
> > > >
> > > >-----Original Message-----
> > > >From: James Howe [mailto:[EMAIL PROTECTED]]
> > > >Sent: Monday, March 19, 2001 2:16 PM
> > > >To: [EMAIL PROTECTED]
> > > >Subject: Re: Performance of struts
> > > >
> > > >If Tomcat's performance is pretty awful, what are some JSP
> > > >implementations
> > > >(commercial or otherwise) that are particularly good?
> > > >
> > > >At 12:10 PM 3/19/2001 -0800, you wrote:
> > > >
> > > >>Struts based apps (or any app that uses custom tags heavily)
> > > >are going to
> > > >>be significantly impacted by the quality of the JSP
> > > >implementation in your
> > > >>container.  Which version are you using?  (NOTE:  Tomcat's performance
> > > >>w.r.t. JSP pages is pretty awful, for example).
> > > >>
> > > >> > Thanks!
> > > >> > keith
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >>Craig McClanahan
> > > >
> > > >James W. Howe                   mailto:[EMAIL PROTECTED]
> > > >Allen Creek Software, Inc.              pgpkey:
> > > >http://ic.net/~jwh/pgpkey.html
> > > >Ann Arbor, MI 48103
> > > >
> > >
> >
> >
> 

Reply via email to