Bug 527784
| Summary: | work with 10'000 system: pages load much slower and/or run into 'service temporary unavailable' | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Petr Sklenar <psklenar> |
| Component: | Server | Assignee: | Justin Sherrill <jsherril> |
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 530 | CC: | cperry, jhutar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-04 13:29:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 525575 | ||
| Bug Blocks: | 462714 | ||
Description of problem: Work with group with 10'000 and Satellite's load go up, either page takes several minutes to load or end in "temporarily unavailable" error due to timeout. Version-Release number of selected component (if applicable): rhel54 x8664, 99gigs of ram sat530 rpm -q spacewalk-java-lib spacewalk-java spacewalk-taskomatic spacewalk-java-lib spacewalk-java-lib-0.5.44-45.el5sat spacewalk-java-0.5.44-45.el5sat spacewalk-taskomatic-0.5.44-45.el5sat spacewalk-java-lib-0.5.44-45.el5sat How reproducible: always during working with 10'000 systems Steps to Reproduce: 1. go to 'System Entitlements' 2. select all system 3. remove / add provisioning entitlement Actual results: See load on Satellite server go up, either page takes several minutes to load or end in "temporarily unavailable" error due to timeout. Expected results: Page loads in reasonable time Additional info: you can simulated huge number of machines by running something like this: 1. create 30 system groups 2. create activation key 1-1 to 1-30 which add system to system groups 3. run on few clients: for a in `seq 1 30`; do { for b in `seq 1 200` ; do rhnreg_ks --activationkey=1-$a --serverUrl=http://gs-bl460cg1-01.rhts.bos.redhat.com/XMLRPC --norhnsd --force --profilename=$b-`hostname` ; done; } done if you have more then 10'000 try steps in reproduced