On Mon, 31 Dec 2001, Ted Husted wrote:
> Date: Mon, 31 Dec 2001 08:58:46 -0500
> From: Ted Husted <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Struts Controller Scalability
>
> Since Java is multithreaded, raw scalability should in fact be better
> with a single servlet. Threads are lighter than running more servlets.
> But, in practice, its the hardware and bandwidth that will determine
> true scalability. The impact of servlets versus threads will be lost in
> the rounding. Every posting I've seen has been consistent on this point.
>
Yep ... in a single-VM environment, the only thing an additional copy of
the controller would do for you is consume more memory. It would make
zero difference in performance.
> For more see,
>
> http://husted.com/struts/resources/performant.htm
>
>
> We are currently in the process of refactoring the nightly build to
> allow the use of multiple servlets to help with team management and to
> easily share functionality between applications. Craig is hard at work
> on this now, and the prospects look very good.
>
Technically, it will still be a single controller servlet when I'm done --
but you'll be able to configure multiple independent Struts applications
(each with their own struts-config.xml file) in a single webapp. If it
all comes together correctly, you should be able to use a
struts-config.xml file as *either* a sub-application within a big webapp,
*or* as the only sub-application (consistent with the current approach),
with no changes.
> But, multiple servlets will be more about code management than
> scalability. For scalability, you need to look at the hardware, database
> latency, and bandwidth. If you have a scalable environment, Struts will
> be able to handle whatever you throw at it.
>
Yep.
Craig McClanahan
>
> RODRIGO CARVALHO DOS SANTOS wrote:
> >
> > Hi,
> >
> > I am thinking in using STRUTS in my next Web Application project. But I
> > am not sure if using only one servlet controller will give me the
> > scalability I need in the project. Another point about having only one
> > controller is about the management of the project. I think will be more
> > dificult to separate the application in distinct areas. I would like to know
> > if some of you have experience or opnions about these concerns.
> >
> > Thank you,
> > Rodrigo.
> >
> > --
> > 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]>
