On Friday 02 of May 2014 11:07:28 Vojtěch Zeisek wrote:
Dne Pá 2. května 2014 11:01:24, C napsal(a):
I'm starting a new thread because the other is filled to the brim with pissing and moaning - I hope everyone keeps that over there.. and OUT of this thread.
So.. I did a clean install of openSUSE 13.1 (full format of all partitions) and then updated to KDE4 Current. I enabled Baloo to index my home (clean home with nothing in it) and a 1TB storage drive (with about 600GB of data... music, video and documents). All other mount points are explicitly excluded. It's been running now for
several hours and I'm seeing: - baloo_file_extractor and it's pegging one CPU core at 100% and
keeping it there
- baloo_file is running a second core at about 95% and keeping it there.
So why would Baloo be churning for so many hours... and is there a way to see what Baloo might be stuck on?
My system has enough gigahertz to drive all this without any noticeable impact. I am wondering though is this... "normal" or have I got something in my 1TB drive that is a troublemaker for Baloo? or something else? Or is this even considered "a problem"?
I think I have similar problem. See https://bugs.kde.org/show_bug.cgi?id=333655 There are also some hints how to track it. The bottleneck isn't CPU or RAM, but HDD... Check atop, iotop. Next KDE:Current update should contain some upstream optimizations in this area, so you might want to test later during the day once it publishes ;-)
Cheers, Hrvoje
Best, V.