[kde-linux] baloo_file_extractor - huge disk usage?

Mark Knecht markknecht at gmail.com
Fri Aug 14 00:28:03 UTC 2015

>> If you have detail questions and would prefer to take it to the gentoo-
>> desktop list (or gentoo-amd64, but the desktop list is more topical),
>> that's fine, or continue here if you like, since it /is/ kde-linux
>> related, and I'm on both this the kde-general and kde-linux lists and
>> those gentoo lists.
> I'll try these ideas out over the next few days and see what happens. I
> generally just use locate to find things so none of this overhead is necessary
> for my normal day to day life.

BTW - I found this on the KDE site:

Baloo/Semantic Search is eating 100% CPU! What do I do?

Just wait. Certain files are very hard or even impossible to Index. At
the moment, this includes for example text files of over 50 megabyte.
When Search finds these, it will try for a fixed time. When it fails,
it will try to find out what file is broken and disable indexing it in
the future. As it indexes files in batches of about 40, it has to find
the problematic file by indexing that bunch in parts: first
half/second half, index problematic half in pieces again, until the
file is found. This can take up to 30 minutes of heavy cpu usage.
Unfortunately, while Baloo will not start to index a new batch of 40
files while on battery power, it continues to determine the broken
file while on battery. This behaviour has been fixed in in KDE
Applications 4.13.1 (it will stop indexing immediately when the power
cord is unplugged) and the time the search for each file can take has
been reduced to about 10 minutes. The Semantic Search team is working
on improving the indexing tools to handle more difficult files.

Amazing...JUST WAIT!

- Mark

More information about the kde-linux mailing list