Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: softfail (nike.apache.org: transitioning domain of
 pid@pidster.com does not designate 209.85.212.45 as permitted sender)
Message-ID: <4B701954.8090405@pidster.com>
Date: Mon, 08 Feb 2010 14:01:56 +0000
From: Pid <pid@pidster.com>
Reply-To: pid@pidster.com
Organization: Pidster Inc
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: users@tomcat.apache.org
Subject: Re: Automatic scaling decisions based on performance metrics
References: <1265634338.2562.34.camel@localhost.localdomain>
In-Reply-To: <1265634338.2562.34.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 08/02/2010 13:05, Shashank Rachamalla wrote:
> Hi
>
> I am currently involved in developing a module which performs automatic
> scaling of application server instances based on their performance. I am
> using JMX to pull data pertaining to server and underlying jvm on which
> the applications are deployed. I can also collect performance data for
> guest operating system.  We are using mod_jk as load balancer. The
> challenging task here is to decide when to scale out and when to scale
> in. Please suggest some strategies used to determine the load at a
> cluster level based on which scaling decisions can be taken. Also can
> any scaling decisions be taken by considering performance statistics of
> a single instance in a cluster.

Excellent!  This sounds like a great idea for an open source project.
Where is it hosted?  I might be interested in contributing...


p

> The following are parameters currently monitored for each server
> instance.
>
> Guest OS
>
> 1) CPU Usage
> 2) Swap Usage
>
> JVM
>
> 1) JVM Free Memory
>
> App Server ( context is / )
>
> 1) Maximum Request Processing Time.
> 2) Number of errors processing requests.
> 3) Number of errors encountered while processing requests.
>
> Regards,
> Shashank
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
>
> www.wipro.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


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