Bug 63923 - Processor Load May Be High Immediately After Install
Summary: Processor Load May Be High Immediately After Install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-22 02:20 UTC by Geoffrey Burling
Modified: 2014-03-17 02:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-01 20:44:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Geoffrey Burling 2002-04-22 02:20:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.18 i686)

Description of problem:
After the install of RH 7.2 is completed, & I am doing a quick check-out of the
system to make sure all items are installed & properly working, I noticed that
the system response was sluggish. Running ``uptime" showed a processor load
above 2.5!

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


How reproducible:
Didn't try

Steps to Reproduce:
1. Install RH 7.2 on an older computer.
2. Run top.
3. Note that on older processors that the load will peak above 2.5
	

Additional info:

Investigation showed that anacron apparently starts slocate within the
first 30 minutes after power up. The first time slocate builds the
database, the cpu gets a work out -- especially on older, slower machines.

This should be documented in order to minimize the surprise on users with slower
machines -- who may also decide to disable slocate until after user
customization is complete.

Comment 1 Michael Fulbright 2002-04-24 16:04:55 UTC
This is a distibution related issue, reassigning.


Comment 2 Bill Nottingham 2005-03-01 20:44:50 UTC
Closing bugs on older, no longer supported, releases. At this point, I don't
think this behavior will be changed. Honestly, I'm unsure where a good place to
document this would be; it's not really a release note issue; it's more of a
general documentation issue.


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