On Sun, Apr 27, 2014 at 8:04 AM, Lars Kruczynski <larskruczynski@gmail.com> wrote:
The point is, that not everybody who uses Linux desktops know to exclude a directory that is written to constantly, and causes Baloo to eat up the system's resources. Does Windows do this? No, it doesn't. Here we have a situation where a "feature" is foisted upon users, and users have to dig into a configuration file to turn it off, and the dev know better than the users and they are _not_ going to put in a GUI switch to turn Baloo off because that's what they want, and what they want matters and that's the end of the story. There is no doubt that Baloo causes high disk I/O on my system and high CPU consumption with multiple torrents running. I killed it in KSysGuard and immediately my system returned to normal. Just because you haven't noticed something does not mean that it does not exist.
Chill a litte. I wasn't defending Baloo. :-P Did you even read what I wrote?
I haven't seen any disk I/O at all. I just checked the Desktop Search settings in "Configure Desktop" and all my drives were excluded.
This is why I hadn't seen any disk I/O. For whatever reason, after upgrading my home was excluded by default. I didnt' exclude it, so post upgrade, Baloo wasn't doing anything.
allowed it to index my NAS drive and my home directory... and there was some serious activity on the NAS for about 10 minutes... I've not noticed anything different at all on my home.. even with torrents running.
This was my observations after enabling.
Some additional info I've dug up: https://forum.kde.org/viewtopic.php?f=154&t=120047#p304335 Which indicates: - To suspend: qdbus org.kde.baloo.file /indexer suspend - To resume: qdbus org.kde.baloo.file /indexer resume - To check that it is suspended:' qdbus org.kde.baloo.file /indexer isSuspended
Over on the Kubuntu forums, they suggest editing this file: $HOME/.kde/share/config/baloofilerc
and editing/adding this line Indexing-Enabled=false
This is currently "how you disable". It's a new "feature" that, like any... needs some rethinking and rework. I've disabled it using the "false" setting and deleted the multi-gig sql index file in $HOME/.local/config If you go read the blog posts by the developer leads (such as this one: http://vhanda.in/blog/2014/04/desktop-search-configuration/ ) you can see that they went about this wrong... they were surprised at the backlash etc etc. Basically they didn't realize that there were users that don't actually.. you know... need Desktop Search capability.
Personally.. I NEVER use indexed searches on my computer. It's a feature I don't need/want. Everything I have is sorted and I know where things are - I'm OCD that way. A desktop search is something I've tried.. and never saw the point in. I am a user who wants it disabled - not because of disk I/O, but that it's a wasted feature on me.
As you can see... I'm on your side here. I don't use search. I don't want search. It's wasted on me. I'll try it, but it's more work for me to search for things than to just go to where I stored it (I'm OCD about keeping my data organized so finding things is easy... for me). C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org