Bug 1370426 - Satellite Web UI Too slow on all the operation
Summary: Satellite Web UI Too slow on all the operation
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Performance
Version: 6.2.0
Hardware: x86_64
OS: Linux
high
urgent vote
Target Milestone: Unspecified
Assignee: Chris Duryee
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 09:59 UTC by Manikandan Somasundaram
Modified: 2019-12-16 06:30 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-01 20:56:57 UTC
Target Upstream Version:


Attachments (Terms of Use)
Foreman-Debug with sql log (7.49 MB, application/x-xz)
2016-08-26 09:59 UTC, Manikandan Somasundaram
no flags Details

Description Manikandan Somasundaram 2016-08-26 09:59:11 UTC
Created attachment 1194278 [details]
Foreman-Debug with sql log

Description of problem:
    
    Customer is facing a web UI slowness issue on all operations regardless of specific once, their Hardware specification matched more them the prerequisite, 
Sar report shows the CPU is idle by 72% approx, however we can see postgres is consuming high cpu

   Customer issue starts the case 01688646, where they are note be able to upgrade a capsule once they have upgraded their satellite server from 6.1 to 6.2, they end up asking them to register the capsule server with Satellite 6.2

please analysis the case


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


How reproducible:


Steps to Reproduce:
1. upgrade satellite from 6.1 to 6.2
2. check the performance of satellite 6.2

Actual results:
Satellite UI is too slow during all the operations the customer tries to do

Expected results:
Smooth UI operation

Additional info:
We have collected foreman-debug with DB log enabled, which has attached in this bug

Comment 8 Chris Duryee 2016-11-01 20:56:57 UTC
I am closing this bug (1370426) in favor of those listed in comment #3.

There is no "closed/broke up into multiple bugs", so I'm marking as closed/notabug.

If the bugs in #3 don't cover the issues you see, let me know and we can investigate further to see if the issue is covered by an existing bug, or needs a new one.


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