Bug 50801 - Install time indicator is very inaccurate
Summary: Install time indicator is very inaccurate
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-03 14:00 UTC by Jos Vos
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-09 22:13:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jos Vos 2001-08-03 14:00:41 UTC
The indicator of the estimated install time is very inaccurate.  The total
time given after installing the first few packages is in most cases only 30
and 50% of the actual time needed. This time slowly increases during the
installation. In the past, the total time decremented a bit during the
install, now the total time increments a lot.

Comment 1 Michael Fulbright 2001-08-09 21:57:51 UTC
How much RAM do you have? The kernel is good about buffering the earliest
packages installed, so the time is short. As the buffers fill the time is longer
because files start to hit the actual disk. Little we can do about it unfortunately.

Comment 2 Jos Vos 2001-08-09 22:13:54 UTC
That system had 128 MB and is a PII 350.  Actually, the total install time
increased to 400% of the time that was indicated after the first 5-10 packages. 
As said, in previous releases the time slowly decreased during the install, now
the deviation is much larger in the opposite direction.

Comment 3 Brent Fox 2001-08-10 22:07:17 UTC
At 128 MB, your computer may be going into swap later on in the install, which
would degrade system performance and could cause the time estimate to vary from
what it was at the beginning of the install.  Like msf said, there's not much we
can do about it.

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