Bug 1281855
Summary: | MiqEmsRefreshCoreWorker exits on xlarge vmware provider on 5.5 | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Alex Krzos <akrzos> |
Component: | Performance | Assignee: | Adam Grare <agrare> |
Status: | CLOSED NOTABUG | QA Contact: | Pradeep Kumar Surisetty <psuriset> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.5.0 | CC: | arcsharm, cpelland, dmetzger, hroy, jhardy, obarenbo |
Target Milestone: | GA | ||
Target Release: | 5.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | perf | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-02-16 20:50:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Alex Krzos
2015-11-13 15:40:47 UTC
Created attachment 1093711 [details]
5.4.3.1 - MiqEmsRefreshCoreWorker Memory usage
Ideal situation where memory usage of this worker never exceeds its defined threshold. RSS Memory usage peaks at 378MiB which is below the appliance's default of 400MiB.
Created attachment 1093713 [details]
5.5.0.9 where MiqEmsRefreshCoreWorker only exceeds threshold during refresh
This memory graph shows MiqEmsRefreshCoreWorker exiting during refresh, and then stabilizing at 395MiB RSS Memory usage after refresh has completed.
Created attachment 1093716 [details]
console output showing MiqEmsRefreshCoreWorker exit storm on 5.5.0.10
This is the worst case scenario, where even after refresh the worker does not settle below 400MiB RSS Memory usage. Note the high user cpu usage at 50-70% due to 2-3 MiqEmsRefreshCoreWorkers starting/exiting concurrently.
With the worker steady state memory around 380-390MiB on 5.4 and increasing to 416MiB on 5.5 I'd argue that an increase in baseline worker memory usage between 5.4 and 5.5 pushed this worker just over the top. In 5.6 we started using PSS for the memory threshold (https://github.com/ManageIQ/manageiq/commit/6583411f3d4634f54db0e404318e0ea594726ce5) and from what I'm seeing this worker is consistently under 400MiB of PSS. With 10240VMs I averaged 300.39MiB PSS over 3 runs for the MiqEmsRefreshCoreWorker. I'll attach the csv and graph of memory usage for the broker and the refresh core workers with 512, 1024, 2048, 4096, 8192, and 10240 VMs. Created attachment 1250943 [details]
5.8 VimBroker and RefreshCore Worker Memory Usage
Graph of VimBroker and RefreshCore Workers RSS&PSS memory usage from 512VMs to 10240VMs
Created attachment 1250945 [details]
Raw data of VimBroker and RefreshCore Worker Memory Usage
Here is the raw data (CSV) from the refresh results used to create the graph.
Seeing as with an "XL VC" aka more than 10,000VMs the worker memory usage is safely under the threshold as of 5.6 I'm going to mark this not a bug as of the 5.6 release (due to the checking of PSS not RSS memory for the threshold) |