Return-Path: 
 <users-return-179559-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 2747 invoked from network); 6 May 2008 09:44:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 May 2008 09:44:42 -0000
Received: (qmail 95347 invoked by uid 500); 6 May 2008 09:44:31 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 95322 invoked by uid 500); 6 May 2008 09:44:31 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 95311 invoked by uid 99); 6 May 2008 09:44:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2008 02:44:31 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of P.Stavrinides@albourne.com
 designates 83.244.143.226 as permitted sender)
Received: from [83.244.143.226] (HELO angus.uk.albourne.com) (83.244.143.226)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 May 2008 09:43:46 +0000
Received: from mail.intern.albourne.com (imap.intern.albourne.com
 [192.168.1.24])
	by angus.uk.albourne.com (8.13.3/8.13.3/Albourne/FW/DNSBL) with ESMTP id
 m469hvf1011897
	for <users@tomcat.apache.org>; Tue, 6 May 2008 09:43:57 GMT
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mail.intern.albourne.com (Postfix) with ESMTP id E650AA1A0005
	for <users@tomcat.apache.org>; Tue,  6 May 2008 10:43:56 +0100 (BST)
X-Virus-Scanned: amavisd-new at 
X-Spam-Score: -4.04
X-Spam-Level: 
Received: from mail.intern.albourne.com ([127.0.0.1])
	by localhost (mail.intern.albourne.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mkoVoTO3SdAl for <users@tomcat.apache.org>;
	Tue,  6 May 2008 10:43:54 +0100 (BST)
Received: from mail.intern.albourne.com (mail.intern.albourne.com
 [192.168.1.24])
	by mail.intern.albourne.com (Postfix) with ESMTP id 61A69B190F78
	for <users@tomcat.apache.org>; Tue,  6 May 2008 10:43:54 +0100 (BST)
Date: Tue, 6 May 2008 10:43:53 +0100 (BST)
From: Peter Stavrinides <P.Stavrinides@albourne.com>
To: Tomcat Users List <users@tomcat.apache.org>
Message-ID: <1373534090.93191210067033988.JavaMail.root@mail>
In-Reply-To: <287627217.92111210065377271.JavaMail.root@mail>
Subject: Re: Tomcat Production Configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.168.255.101]
X-Mailer: Zimbra 5.0.5_GA_2201.RHEL5_64 (ZimbraWebClient - FF2.0
 (Linux)/5.0.5_GA_2201.RHEL5_64)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Old-Spam-Flag: NO
X-Old-Spam-Status: No, score=-4.04 tagged_above=-10 required=6.6
	tests=[ALL_TRUSTED=-1.8, AWL=0.359, BAYES_00=-2.599]

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.Stavrinides@albourne.com>
To: "Tomcat Users List" <users@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