Bug 162491
Summary: | Slow search for package names on RHN server | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Christopher Basquez <cbasquez> |
Component: | Server | Assignee: | Mike McCune <mmccune> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jeff Browning <jbrownin> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 360 | CC: | dparker |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | sat530 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-10 18:24:22 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: | |||
Bug Blocks: | 472497 |
Description
Terry Jones
2005-07-05 15:40:32 UTC
I have attached the output to the script originally supplied by J Slagle on 4/19 to Dresdner Kleinwort Wasserstein the work I did had no effect on the speed. Myself and Vlad both tested package searching on webqa and it seemed to return in reasonable amounts of time. I think it would be worth testing out package searching on a fully sat-synched sat to make sure there isn't some difference. I'll take a look at this and report back. I tested out package searching on a sat with lots of channels/packages and it was very snappy. Searches returned in 1 second or less. TESTPLAN: 1) Login to a sat that has multiple channels synched with a large number of packages (1000+) 2) Search -> Packages 3) type a name, libjpeg for example 4) click on the name verify that none of the steps take an unacceptable amount of time (2-3 seconds or more). on_dev Verified. Search takes roughly 1 second when searching through 10,000 packages. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html |