Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4FE0BB4D.9030500@yahoo.es>
Date: Tue, 19 Jun 2012 19:47:57 +0200
From: =?UTF-8?B?TWlndWVsIEdvbnrDoWxleiBDYXN0YcOxb3M=?=
 <miguel_3_gonzalez@yahoo.es>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: heap memory issues
References: <4FDFAD06.40505@yahoo.es> <4FDFFA67.4090503@tmbsw.com>
In-Reply-To: <4FDFFA67.4090503@tmbsw.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 19/06/2012 06:04, Terence M. Bandoian wrote:
>  On 1:59 PM, Miguel González Castaños wrote:
>> I know, but how do I know how much ram to assign in a 64 bits jdk? We 
>> are planning to move to a bigger server (hopefully 16 or 32 gb).
>>
>> Miguel
>
> 16 or 32 GB?  Is this a medical image processing system?  A control 
> system for a space flight?  Sorry for the sarcasm but that just seems 
> like an enormous amount of memory.
It depends on how many concurrent users you have. If you have plans of 
having more than 1000 people accessing at the same time your server you 
have to be ready and I'm not talking about short sessions, but long 
sessions and intense database access.

Anyway, before we move to a bigger server, we need to get a stable 
webapp and check which load can handle the current server.

Miguel


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org