[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 331932] add option for disabling indexing
From:       <lucke () o2 ! pl>
Date:       2014-05-06 15:05:23
Message-ID: bug-331932-17878-rryAE0wLW4 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=331932

lucke@o2.pl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lucke@o2.pl

--- Comment #57 from lucke@o2.pl ---
To clarify a bit about deadline: it seems that Ubuntu changed to deadline io
scheduler (elevator) with the 14.04 release (its release notes mention the
change). Deadline, unlike the previous default io scheduler, cfq, doesn't
support io priorities or classes (unless something changed and the available
documentation is outdated), so with it you can't tell processes to use the disk
only when other processes aren't using it. Cfq seems to be a better desktop
option (while deadline might be preferable on servers), if only because of
those io priorities/classes (it should generally offer better
interactivity/responsiveness, including starting programs quickly when the disk
is busy with something else[1]; in the Windows world, Vista introduced io
priorities, and their search takes advantage of that). It is a mystery to me
why Ubuntu made the change (cfq is still the kernel default; Ubuntu started
using one kernel for desktops and servers some time ago, thus they stopped
having a server kernel with deadline as default). I fail to google out any
discussion concerning the change in Ubuntu. It seems some people were having
better boot up/KDE loading performance with deadline, some years back.

baloo is a program that would be the prime beneficiary of io
priorities/classes, and, as luck would have it, in one of the most popular
distros introduction of baloo coincides with the change to an io scheduler not
supporting them. There's now a bug report open about it[2].

One can change the default io scheduler to cfq by adding "elevator=cfq" to the
bootloader's kernel line or it can be changed on the fly by issuing "echo cfq >
/sys/block/sdX/queue/scheduler", although I don't know if it would have an
instant effect on the running baloo processes. 

I would be interested to hear from people having problems with baloo if
changing the io scheduler helps. 

My 8 years old PC works well with baloo indexing.

[1] http://algo.ing.unimo.it/people/paolo/disk_sched/results.php
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310402

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]