| Summary: | Excessive swapping in 5.6 beta appliances | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Milan Falešník <mfalesni> |
| Component: | Appliance | Assignee: | Gregg Tanzillo <gtanzill> |
| Status: | CLOSED WORKSFORME | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.6.0 | CC: | abellott, cpelland, jhardy, obarenbo, thenness |
| Target Milestone: | Beta 2 | ||
| Target Release: | 5.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | appliance:perf | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-04-18 10:47:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Bug | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Attachments: | |||
Created attachment 1147651 [details]
evm.log file up to the point where the evmserverd service is stopped
Created attachment 1147652 [details]
standard top reports showing pid count growth, memory and swap growth and cpu idle
Created attachment 1147653 [details]
top output for detailed process analysis
Created attachment 1147655 [details]
summary page showing counts of processes by worker type
So we believe this was all caused by appliances being sent to the wrong (smaller) osp flavor, appliance is running much better under 8GB of memory. |
Created attachment 1147617 [details] screenshot of top on an appliance managing QE's vsphere55, ~10 minutes after adding it. Description of problem: In QE, we have discovered that the 5.6 appliances develop excessive swapping with the same load as eg. 5.5 takes without problems. This has bad effects on our QE infrastructure. Version-Release number of selected component (if applicable): 5.6.0.0-beta2 How reproducible: always Steps to Reproduce: 1. Deploy the appliance 2. Add a provider (eg. QE's vsphere55) 3. Wait and watch eg. top Actual results: Some swapping (in hundreds of MB) develops quite fast (~5min). We have also seen appliances taking 6G of memory, those probably managed more providers Expected results: Nothing special happens. Additional info: