They seem to be itching for benchmarks though, so I'll give it to them by building a single, then multi-servlet app and using Introscope with some load test simulators. I was hoping somebody in a situation such as myself already had done it.
It's a shame that you're required to do this because an explanation of how Java threading works should suffice. Simply put, it doesn't matter how many servlet instances exist, it only matters how many threads are running through one instance at a time.
David
Now the next matter of opposition I'm getting is does struts work well in a distributed environment for example load balancing. I will post this a separate thread with what I have told them already.
"Craig R. McClanahan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>
> On Thu, 22 May 2003, Tin Pham wrote:
>
> > Date: Thu, 22 May 2003 00:09:09 -0400
> > From: Tin Pham <[EMAIL PROTECTED]>
> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Struts Performance - Any Benchmarks?
> >
> > Hi, I have been scouring the internet with no results.
> >
> > Does anybody have any resources on the performance of Struts
applications.
> > Any
> > benchmarks versus standard development.
> >
> > One "bottle-neck" brought up by members of my team is the single action
> > servlet everything must pass through. Are there currently or going to be
> > programming solutions to this?
> >
>
> If your team believes that this issue is a bottleneck, then some training
> and a more complete understanding of how multithreading works in Java
> might be appropriate -- the fact that a single instance of the action
> servlet (and of the actions themselves) has zero impact on performance,
> and it reduces memory consumption of your app by avoiding useless extra
> copies.
>
> > For example, maybe we can have more than one action servlet and use a
> > different mapping.. ie, instead of *.do, *.jspx ? But then would global
> > forwards from the two different actions still work?
> >
>
> This won't work, but not for performance reasons -- Struts supports only a
> single mapping to the controller servlet, and only one controller servlet
> per webapp.
>
> > Personally, I argue that we should simply go to load balancing if it
comes
> > to
> > that and adding more servlets wouldn't do much anyway. From my
rudimentary
> > undestanding of java servlets, other resources will choke on you way
before
> > the single servlet chokes anyhow.
> >
>
> See above -- the most important factors in webapp performance have nothing
> to do with this issue at all. In fact, the most important factors are
> typically:
>
> * Overall application architecture (things like caching where it is
> appropriate, but not doing premature optimization -- there are lots
> of good books on optimizing server-side Java apps around to draw
> ideas from).
>
> * Database performance (be sure to use connection pooling effectively)
>
> * Network performance
>
> * The quality of the code generated by your JSP page compiler
> for pages using lots of custom tags.
>
> Craig McClanahan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
