https://bugs.kde.org/show_bug.cgi?id=476752
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Stefan Brüns from comment #2)
> There is also the IO throttling happening when the computer is in use
> (according to KIdleTime).
My experience is that when baloo thinks the system is not busy and says
kf.baloo: Not busy, fast indexing
you can use a full CPU core. As soon as you ask the system to do "anything",
baloo switches to
kf.baloo: Busy, paced indexing
and you get a noticeable pause after indexing each batch of 40 files. (This is
with content indexing...)
> ... pushing this up too much will result complains, flame wars etc. And "too
> much" is highly system dependent ...
If you have a "turbo" button, you are not changing the defaults, it's then a
user choice and you can ignore the flame wars :-)
Maybe increase the number of files indexed per batch. Maybe switch to "fast
indexing". Maybe increase the "MemoryHigh" in the systemd unit file.
I think it's a useful option...
--
You are receiving this mail because:
You are watching all bug changes.
