Performance Testing Environment
--------------------------------
Web Server
CPU: 4 Core processor
RAM: 14984 MB
OS: AMI(amazon linux) --64 bit
App Server
CPU: 4 Core processor
RAM: 14985 MB
OS: AMI(amazon linux) --64 bit
DB Server
CPU: 4 Core processor
RAM: 14985 MB
OS: AMI(amazon linux) --64 bit
Deployment Information
-----------------------------------
Web Server (Apache) : Serving static files, images, javascripts, CSS etc.
App. Server (Jboss GA 5.1.0) : An eCommerce application
Database Server (mysql Ver 14.14 Distrib 5.5.28) : The DB schema for the e-Commerce application.
Background on site usage
--------------------------------------
The site currently supports 700 Active users (per Google Analytics) and CPU utilization stayed at 40 % when that many users were active in the site. The 'maxThreads' configuration in server.xml file is set at 700, and ConnnectionPool size has also been set at a value matching the demand. JVM tuning had been done subseqent to the results obtained as a result of load testing the application iteratively.
The above usage case has been supported by running a single instance of Jboss.
Other info : Jboss has been slimmed as per the recommendations in the web site
Questions
------------------
I. In anticipation of a higher demand, 2000 Active users at peak, we are considering the following strategies
a. Increase the parameters like 'maxThreads', max-min connection pool sizes, and achieve the capacity to address that many users.
b. Have another instance of Jboss running in the same box, and cluster that with the former, and have the configuration parameters stated in #I.a. to support 1000 users on each of those Jboss instances.
Which among the above will be a better option? - The CPU utilization on the App Server machine can go up to 70 %.
Are there other candidate strategies that provide better value for the investment already done?
II. Are there any Jboss/ Operating System configuration tuning specific to AWS cloud deployments?