Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 93413 - updatedb not sensitive to system usage
Summary: updatedb not sensitive to system usage
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High enhancement (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-21 05:40 UTC by kalium
Modified: 2005-05-21 11:28 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kalium 2005-05-21 05:40:57 UTC
updatedb is slowing down the system very badly.

Reproducible: Always
Steps to Reproduce:
1. Switch on PC.
2. Wait until updatedb starts.
3. Do something else and you'll notice that your harddisk throughput gets very bad.



Expected Results:  
updatedb should sleep when there is other avctivity on the system, especially
user activity. Maybe we could enhance the cron/anacron daemons to start/kill
updatedb and other extreme load producing processes...
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2005-05-21 06:19:48 UTC
This depends on the system and you're responsible for your system. Edit the cron
script(s) to start updatedb with lower priority.
Comment 2 kalium 2005-05-21 07:25:05 UTC
Lower priority does not mean that there won't be signficant disk access. It is
already reniced to level 10...
Comment 3 Paul Waring 2005-05-21 11:28:17 UTC
Try starting it with level 19 priority (which I believe is the lowest you can go
on Linux), or just delete the cron job and run updatedb manually say once a week
(you shouldn't need to run it much more frequently unless your file system is
changing a lot).