Bug 82719 - estimated install time way off
estimated install time way off
Status: CLOSED DUPLICATE of bug 81479
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-25 02:13 EST by John Mellor
Modified: 2008-01-17 12:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Mellor 2003-01-25 02:13:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115

Description of problem:
The estimated install time should remain fairly constant after a few packages
have been installed, and fairly accurately reflect the estimated installation time.

In the observed case, the installation estimated time for 618 packages ballooned
from an initial 13 minutes to just under 35 minutes.  The estimation code is
obviously broken.

Possible unhandled calculation factors: 1GHz athlon, 512MB pc133 SDRAM, 4GB ATA
disk with slow transfer rate of ~3MB/s (per hdparm timings), 56xCDRW.  Also
noted that postinstall script runtimes incorrectly do not seem to be factored
into the calculation.

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


How reproducible:
Always

Steps to Reproduce:
1.Install product
 

Actual Results:  Product correctly installed in over twice the calculated time
estimate.

Expected Results:  Actual install time should closely match the expected time.

Additional info:
Comment 1 Michael Fulbright 2003-01-27 11:56:08 EST

*** This bug has been marked as a duplicate of 81479 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:23 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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