You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Peter Stavrinides <P....@albourne.com> on 2008/05/06 11:16:17 UTC
Tomcat Production Configuration
Hi All
My question concerns optimizing Tomcat.
Our setup is roughly this:
- Dual Quad Core with 8 gigs memory (4 gigs dedicated for Tomcat)
- Single instance of Tomcat6
- Single web application (Java Servlet)
- AJP connector
A little about the application:
The site is relatively low volume, however traffic spikes when our newsletter is sent out. The application is complex and connects to a large research database serving a number large pages with reports, charts, data tables etc, which are generated dynamically from live data... sessions tend to get quite large. My thinking is that I should be supporting in the region of 200 to 300 sessions as a minimum.
So given this setup, how should I configure the connector with regards to: maxThreads and any other relevant attributes. I am thinking of about 300 threads? I would be grateful for your advice.
Thanks for your help,
Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Production Configuration
Posted by Pid <p...@pidster.com>.
Hi,
I'm not sure if this will apply in your case, but I found that
offloading the mail to a second (relatively low spec as it happens)
local machine improved the mail output rate considerably - mailouts went
in about 1/4 of the previous time.
The local mail server was using CPU cycles and the servlet app using
lots of memory in our case - combined on one machine the overall load
rocketed and the web app seemed to suffer most.
Not exactly the answer you were looking for I guess, but tinkering with
the connector attributes didn't actually seem to make a great deal of
difference to us.
p
Peter Stavrinides wrote:
> Sorry I forgot to add:
>
> <Connector port="8009" protocol="AJP/1.3"
> connectionTimeout="20000"
> enableLookups="false"
> redirectPort="8443" maxThreads="300"/>
>
> We also run under SSL, which is taken care of by Apache.
>
>
> ----- Original Message -----
> From: "Peter Stavrinides" <P....@albourne.com>
> To: "Tomcat Users List" <us...@tomcat.apache.org>
> Sent: Tuesday, 6 May, 2008 12:16:17 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul
> Subject: Tomcat Production Configuration
>
> Hi All
>
> My question concerns optimizing Tomcat.
>
> Our setup is roughly this:
> - Dual Quad Core with 8 gigs memory (4 gigs dedicated for Tomcat)
> - Single instance of Tomcat6
> - Single web application (Java Servlet)
> - AJP connector
>
> A little about the application:
> The site is relatively low volume, however traffic spikes when our newsletter is sent out. The application is complex and connects to a large research database serving a number large pages with reports, charts, data tables etc, which are generated dynamically from live data... sessions tend to get quite large. My thinking is that I should be supporting in the region of 200 to 300 sessions as a minimum.
>
> So given this setup, how should I configure the connector with regards to: maxThreads and any other relevant attributes. I am thinking of about 300 threads? I would be grateful for your advice.
>
> Thanks for your help,
>
> Peter
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat Production Configuration
Posted by Peter Stavrinides <P....@albourne.com>.
Sorry I forgot to add:
<Connector port="8009" protocol="AJP/1.3"
connectionTimeout="20000"
enableLookups="false"
redirectPort="8443" maxThreads="300"/>
We also run under SSL, which is taken care of by Apache.
----- Original Message -----
From: "Peter Stavrinides" <P....@albourne.com>
To: "Tomcat Users List" <us...@tomcat.apache.org>
Sent: Tuesday, 6 May, 2008 12:16:17 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: Tomcat Production Configuration
Hi All
My question concerns optimizing Tomcat.
Our setup is roughly this:
- Dual Quad Core with 8 gigs memory (4 gigs dedicated for Tomcat)
- Single instance of Tomcat6
- Single web application (Java Servlet)
- AJP connector
A little about the application:
The site is relatively low volume, however traffic spikes when our newsletter is sent out. The application is complex and connects to a large research database serving a number large pages with reports, charts, data tables etc, which are generated dynamically from live data... sessions tend to get quite large. My thinking is that I should be supporting in the region of 200 to 300 sessions as a minimum.
So given this setup, how should I configure the connector with regards to: maxThreads and any other relevant attributes. I am thinking of about 300 threads? I would be grateful for your advice.
Thanks for your help,
Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org