*** This bug is a duplicate of bug 134692 ***
https://bugs.launchpad.net/bugs/134692
** This bug has been marked a duplicate of bug 134692
updatedb cron job should make use of ionice
--
slocate daily anacron job makes system feel slow
https://bugs.launchpad.net/bugs/13671
You received
Hi,
I looked into ionice CFQ some time ago. The use of ionice didn't
much help with the updatedb-run-and-system-gets-really-slow-to-interact-
with problem.
To be really sure, if the 'ionice' command is the problem, I wrote a
kprobe-module to check if the ionice value is present in the
I tried to measure the impact of ionice on updatedb when running in parallel
with a full Eclipse workspace rebuild, a CPU- and disk-intensive process.
Results below, there are two measurements per item (this is Gutsy on a Pentium
M 2GHz notebook, 7200RPM disk):
Build alone: 50s, 52s
Build with
Well I could have searched a bit myself: it seems I am using the CFQ scheduler:
$ cat /sys/block/sda/queue/scheduler
noop anticipatory deadline [cfq]
(I guess the brackets show the selected scheduler).
So it seems that ionice is not doing its job properly. Any idea about why? This
is the
If the schedutils package - which includes ionice(1) - is installed (and
cfq is the active io scheduler on the relevant devices), we can run
updatedb with a very low IO priority. This might improve response times
for other applications while updatedb is running, as the cfq IO
scheduler will permit
