Bug 240361 - Conga storage UI front-end is too slow rendering storage
Summary: Conga storage UI front-end is too slow rendering storage
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: conga   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Ryan McCabe
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-16 18:35 UTC by Ryan McCabe
Modified: 2009-04-16 22:24 UTC (History)
6 users (show)

Fixed In Version: RHSA-2007-0640
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 15:37:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0640 normal SHIPPED_LIVE Moderate: conga security, bug fix, and enhancement update 2007-11-08 14:19:24 UTC

Description Ryan McCabe 2007-05-16 18:35:12 UTC
When a storage report request is made for a system, and that data is used to
render the storage pages, the front-end can take over 60 seconds to render
results that were retrieved in, on average, somewhere between between 3 and 8

Comment 1 RHEL Product and Program Management 2007-05-21 22:23:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 2 Ryan McCabe 2007-06-04 18:06:43 UTC
I believe I've fixed the worst of this. There are probably some more tweaks that
can be made, but I've killed the major bottlenecks.

Comment 5 errata-xmlrpc 2007-11-07 15:37:42 UTC
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 the 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.


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