What do you mean by simultaneous users? Do you mean 100 users all doing the
same thing at the same time?
In my practical experience, the performance is not limited by struts, but
limited by EJB performance. We recently did stress tests on a struts-based
site, and actions with no EJB component scaled to a much higher level than
those with one.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
NetRexx: http://www.multitask.com.au/NetRexx.nsf
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 26/07/2001 04:48
PM -----
Struts Scalability in a Large Production Environment
All,
I have been doing a lot of research into Struts recently. My question is
about performance and scalability. First the definitions:
Performance = good response time to users
Scalability = good response time to a large number of simultaneous users.
Usually this is a logarithmic curve that reaches a point where the server
has difficulty sustaining the load.
Struts will only be used for presentation logic. My Action classes in this
framework will access separate business objects that will then access a BEA
application server to perform the necessary business logic (EJB's) and
return the results. This will be a large production environment with a
large number of simultaneous users if we decide to implement this way. The
Web servers will be load balanced. Even so, I don't want to implement a
framework which requires me to throw a bunch of hardware at it after all is
said and done.
Does someone have some practical experience of the performance and
scalability of the Struts framework with an overhead of 100 simultaneous
users? What about 1000?
Is there any kind of advice that anyone can offer me before I head down
this path in relation to scalability?
Thanks,
Brian
Previous Document (Embe (Embe Next Document
dded dded
image image
moved moved
to to
file: file:
pic00 pic18
041.p 467.p
cx) cx)
Return to View
(Embedded image moved to
file: pic06334.pcx)
pic00041.pcx
pic18467.pcx
pic06334.pcx
