Created attachment 1177420 [details]
Two stacked graphs displaying worker cpu usage during 4 C&U workload scenarios

Description of problem:
I ran 4 sets of 4 hour long workloads where:
1. Provider is added
2. C&U is turned on
3. Metrics collection and processing is occurring transparently to the user

Each workload uses a different provider:
Small/Medium/Large/XLarge - all of VMware type

Over two different appliance versions:
5.6.0.13
5.5.5.0

I then compared system resource utilization and found that the MiqVimBrokerWorker is utilizing the CPU far more in 5.6.0.13 than it previously did in 5.5.5.0

Version-Release number of selected component (if applicable):
5.6.0.13

How reproducible:
When compared correctly it is reproduced

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
This appears to be exacerbating a bottleneck in that we have a single point to communicate to the provider to capture metrics and that single point is using far more CPU than it used to in older builds.  Additionally more CPU utilization is occurring on the 5.6 builds (We are using the cpu more)


Attached Graph:
Top is 5.6, bottom is 5.5, each 4 hour segment is the next workload(C&U) scenario(Different provider) in order of 4 hours of small, 4 hours of medium, 4 hours of large, and 4 hours of xlarge. Note the filling out of available CPU on the 5.6 towards the Large/Xlarge scenarios.