On 05/02/2014 07:59 PM, Vojtěch Zeisek wrote:
Dne Pá 2. května 2014 17:56:36, C napsal(a):
On Fri, May 2, 2014 at 12:41 PM, šumski
wrote: 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 ;-)
I've just now updated and rebooted just for good measure (yah I know I didn't need to, but this way I'm sure that everything is loading properly post update).
Baloo had finished whatever it was doing sometime in the past 2 hours (so it ran the indexing process for around 8 hours over a drive with 600GB of media). Prior to the update there was no indexing occurring. After the update.. still quiet. Whatever Baloo was doing to chew up the CPU and I/O is not starting up again.
I have same experience. After upgrade, Baloo is still consuming 30-40 % of CPU. but not so much I/O, so that the computer is usable, although it is not perfect. ;-) Definitely change for better, thanks devs! All the best, V.
not for me, in my PC=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz, OS=opensuse 13.1 KDE= 4.13.0 I used the new-advanced-baloo-configuration-tool, an it is very ok, to start and stop baloo indexing, but, even leaving baloo indexing active for all the night, the laptop was unusable when baloo indexing is active, my system monitor ksysguard doesn't identify more than 10% baloo cpu usage, but laptop isn't unusable likewise..:-) :-) :-) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org