Description of problem:

120 users logged in to one conductor instance (log in times separated by 5 seconds) can each:
 - create an application blueprint
 - launch an instance from that blueprint (using mock provider)
 - go to the monitor page and see the launched instances (although time to bring up the monitor page grows - logged in a separate BZ)

(See jmeter test output 'csv file' resultsTable120.csv)

Scaling that up to 200 users and conductor no longer operates and launch all the required instances successfully. Tried this test twice. 
 - In the first attempt, 0 instances were launched ( See jmeter test output 'csv file' resultsTable200_0.csv)
 - In the second attempt, 3 instances were launched but even access the conductor/users page starts to throw 503 "Service Temporarily Unavailable" errors. (See See jmeter test output 'csv file' resultsTable200_0.csv)

rpms tested:

rpm -qa |grep aeolus
rubygem-aeolus-cli-0.3.0-14.el6.noarch
aeolus-configure-2.5.0-18.el6.noarch
aeolus-all-0.8.0-41.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-0.8.0-41.el6.noarch
aeolus-conductor-daemons-0.8.0-41.el6.noarch
aeolus-conductor-doc-0.8.0-41.el6.noarch