Since this is your first Struts app, I suspect that you can't say for sure how it will perform on Tomcat or any other container. I'd suggest that you find out what your exact requirements are and then figure out what you'll need to properly address them. Here's the approach I would take:
1. Gather requirements. What are the reqs in your system for response time, concurrent users, etc. 2. Create a proof of concept. Implement some of your application components. I'd go with a simple one (to make sure it works), a "typical" one (to measure typical usage), and a complex one (to ensure complex components can be created successfully). 3. Test the proof of concept. Download every container you can get your hands on and deploy the POC on each container on the same machine. Measure it against JProbe or some profiler. Even a home-grown profiler can be useful. 4. Publish the results. How close can your POC come to meeting the requirements on the test machine in each container? How do they compare? What will have to be done to come closer to the requirements? What hardware will be required? It's not extremely difficult to get fairly accurate measurements and determine what needs to be done to acheive performance goals. But you have to know what the goals are, and you have to test to determine how to reach the goals. I believe there's no excuse for getting to the end of a project and realizing it doesn't perform. It just doesn't take *that* much effort to do it up front and regressively do it throughout the process. HTH, Greg > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 22, 2002 9:17 AM > To: Struts Users Mailing List > Subject: Re: html taglib usage slooow > > > > > This topic comes up from time to time and it seems that I am > never happy with > the solution(s). > > There seems to be two main answers: > 1 - do not use so many tags. > 2 - find an Servlet Container that will handle tags in a > speedy manner. > > Have I missed any? > > As for answer one > - I am currently beginning the design stage of a project > that will use struts ( > our first one) and am looking forward to finding tags that > clean up my code. > I could probably get away with not using the bean write tags > for all my labels > but I am experimenting with the format attribute for currency > and dates ect. > It seems that fifty tags is a number that comes up from time to time. > How does looping over tags factor into this? > > As for answer two: > - Craig mentioned in this post that the nightly build of > tomcat handles this > much better. The nightly build thing will be a tough sell > for me. Is there a > particular production container that (at this time) is known > for it's efficient > tag handling (code generation, pooling ect) ? > > > Summary: > We are doing an internal A/R application. If you include > labels, it is not hard > to exceed 50 tags. > I would be disappointed to find out that I cannot make use of > the full power of > Struts, and have to replace some tags with a scriplets. > But at the same time I would like to know of some of these > issues that I might > face. > > Thanks. > > > > > > > > > Victor Hadianto <[EMAIL PROTECTED]> on 05/21/2002 06:33:07 PM > > Please respond to "Struts Users Mailing List" > <[EMAIL PROTECTED]> > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > cc: > > Subject: Re: html taglib usage slooow > > > On Wed, 22 May 2002 02:11, you wrote: > > On Tue, May 21, 2002 at 12:01:06PM -0400, Galbreath, Mark wrote: > > > Precompile the JSP. > > > > Have tried that, does not help. Even after compiling, it's > really slow. > > This is not going to work .. read on . > > > > > It seems, the problem is within the taglib implementation - > either in the > > appserver or within struts. > > > > Erich, > > I have posted the similar issue weeks ago in the mailing > list. We too found > that the use of html:taglibs are really slow. After running > the profiler we > found that (in our case) the primary slowdown spot is the > <bean:write> tag. > We have hundreds of this tag in our page (it's a really > complex page I assure > you). > > Drilling down again to find the root cause I found the > problem was that > bean:write tags call request.getLocale(). > request.getLocale(), for some > reason we couldn't fathom, took ages to execute. > > This is why, in our situation, that the rendering of the page takes in > average 80% of the time, even longer than multiple server > roundtrips to the > EJB server, action class logic and some other overheads. > > grrr ..... > > -- > Victor Hadianto > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
