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

List:       kde-bugs-dist
Subject:    [Baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays
From:       Martin Steigerwald <Martin () Lichtvoll ! de>
Date:       2014-05-15 12:38:13
Message-ID: bug-333655-17878-ZbkfVipAVQ () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #47 from Martin Steigerwald <Martin@Lichtvoll.de> ---
Vojtěch, the script needs some uncompressed text files in /usr/share/doc. And
beware: It may eat your disk. Maybe reduce COUNT to 5 depending of amount of

find /usr/share/doc -name "*.txt" | wc -l

or use COUNT=1 or COUNT=2 and raise from there – unless you can let your system
sit at it for a while. But you can also stop baloo after say 5 or 10 minutes, I
think.

If that what you have is without the script running and you can reproduce it by
other means, that may be fine to. Process accounting is important, as then we
can see what amount of I/O baloo generates and what other processes generate.
This may give hints which processes generate I/O that baloo_file indexes
thereafter.

I am pondering about a simple baloo-top which shows which files it indexes at
any given moment, but first I write on my article.

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