Description of problem:

Added 100 users, 1 image and 100+ deployments to one Conductor instance.  Then started three browsers and pointed them to the Monitor Overview page (/conductor/pools) of this Conductor instance. The three browsers used:
 - FF 11.0 ( on Fedora 16)
 - FF 10.0.3 (on RHEL 6.2)
 - Chrome 18.0.1025.151 (on Fedora 16)

The three browsers where left open but untouched for 48+ hours. After that time, started working with Conductor through the three browsers. When accessing the /conductor/pools page, the Role Grants page and other pages that take time to load, Conductor showed slowed performance and it was possible to see the pages painting on Chrome. Firefox showed less of a performance hit and no painting issues were visible on FF 11.0 or 10.0.3.

See attached screenshots capturing pages painting in Chrome. Note that only three users were logged in to, and working with, the Conductor instance when the painting was visible.

  
rpms tested:

rpm -qa |grep aeolus
aeolus-conductor-daemons-0.8.7-1.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.1-1.el6.noarch
aeolus-configure-2.5.2-1.el6.noarch
aeolus-conductor-0.8.7-1.el6.noarch
aeolus-conductor-doc-0.8.7-1.el6.noarch
aeolus-all-0.8.7-1.el6.noarch