On 3/17/06, David Rees <drees76@(protected):
> On 3/17/06, Rajeev Jha <jha.rajeev@(protected):
> > Then, the other bottle-neck is, integrating with apache. If we run
> > tomcat APJ APR and apache is the front end then apache would also be
> > hard pressed to do 1024 keep-alive connections. I can try event MPM or
> > worker modules. Does this look ok ?
> >
> > Active child processes - 32
> > Server Limit - 64
> > ThreadsPerChild - 32
> > MaxClients - 1024
>
> What's your ratio of Apache to Tomcat instances? You may want to look
> into using squid as a reverse proxy to Tomcat, it is very good at
> supporting a huge number of concurrent clients without having to spawn
> a thread or process for each one.

But pushing dynamic content with squid? I doubt it will work. However,
squid is using select reads instead of tomcat's blocking reads, and
could reduce the number of threads, but I have seriously doubts with
keepalives, have you actually tested it? :-)



>
> -Dave
>
Leon

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)