Bug 1378975 - Swap observed due to puma on UI appliances, causing unresponsive UI [NEEDINFO]
Summary: Swap observed due to puma on UI appliances, causing unresponsive UI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Performance
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Nick LaMuro
QA Contact: Pradeep Kumar Surisetty
URL:
Whiteboard: perf:ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 18:03 UTC by Jerome Marc
Modified: 2018-03-30 17:21 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-08 13:30:08 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
nlamuro: needinfo? (dajohnso)


Attachments (Terms of Use)
Troubleshooting results for free, smem, smem -W and vmstat commands (2.33 KB, application/zip)
2016-09-23 18:03 UTC, Jerome Marc
no flags Details

Description Jerome Marc 2016-09-23 18:03:49 UTC
Created attachment 1204244 [details]
Troubleshooting results for free, smem, smem -W and vmstat commands

Description of problem:
UI appliances become very slow after some time on the MBU Lab. Looking at the UI appliances, we observe memory swap happening, specifically due to puma. Restarting the appliance is the only fix.

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

How reproducible:
Always

Steps to Reproduce:
1. Have CloudForms setup in a Production environment (e.g. 2 UI appliances, 1 BD master, 9 worker appliances) 
2. Give access to users and let them use CloudForms

Actual results:
Over time, swap will start occurring on the UI appliance. Analysis seems to point at Puma (see command results attached).

Expected results:
Swap should not happen. These appliances are 8GB RAM, with 4 UI workers each.

Additional info:
Happy to share the environment credentials for further troubleshooting.

Comment 2 Jerome Marc 2017-01-23 22:24:00 UTC
Same issue experienced in 5.7.

Comment 17 dmetzger 2018-01-08 13:30:08 UTC
Closing this 5.6 ticket based on the work / investigation completed to the point. If the problem is found reproducible in a more current release a new ticket should be created. My understanding at this time is there have been problems reproducing this reliably on 5.6 and it has not be reported on newer releases.


Note You need to log in before you can comment on or make changes to this bug.