Description of problem: With 120 + users logged in, (with or without active deployments), the time to access the Monitor page (conductor/pools) increases rapidly. Steps to Reproduce: 1. 120 users logged in and actively using conductor 2. Access the Monitor page 3. Measure the length of time for the page to open See the test result file attached. Test involved 120 users (120 instances were launched). The Sample Time to access the conductor/pools page runs into the 9+ minute range. Sometimes, the page will not even open - resulting in 503 Service Temporarily Unavailable Error or Proxy Error. 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
Created attachment 569765 [details] test results - 120 users
*** This bug has been marked as a duplicate of bug 802908 ***