On Fri, May 2, 2014 at 11:07 AM, Vojtěch Zeisek
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.
I looked into atop and it at least reports the same as I'm seeing elsewhere... PID TID RUID EUID THR SYSCPU USRCPU VGROW RGROW RDDSK WRDSK ST EXC S CPUNR CPU CMD 1/2 18827 - username username 1 5.19s 4.75s 0K 0K 0K 0K -- - R 0 100% baloo_file_ext 1333 - username username 2 4.56s 4.18s 0K 0K 0K 0K -- - R 1 90% baloo_file C. -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org