I dislike adding the ability to switch off the indexer as the a traditional user has no knowledge about indexing. They do however understand folders and where stuff is searched - hence the widget to exclude folders.

Currently, if your HOME directory is added to the list of exclude folders, then baloo_file will be be switched off. So, it's not completely obvious, but it is there.

I'm marking this bug as WONTFIX. Feel free to re-open if you disagree strongly.

Well, I disagree. I agree that with *new* hardware like SSD and stuff, you won't notice the indexer. It's a no brainer. However, even on my notebook which is about two years old, the indexer really hurts performance. I just have a normal HD with encryption enabled. Every disk access slows the computer down. Especially during the initial run of the indexer, the laptop is hardly usable. I'm not exaggerating.

(In reply to comment #2)
> Well, I disagree. I agree that with *new* hardware like SSD and stuff, you
> won't notice the indexer. It's a no brainer. However, even on my notebook
> which is about two years old, the indexer really hurts performance. I just
> have a normal HD with encryption enabled. Every disk access slows the
> computer down. Especially during the initial run of the indexer, the laptop
> is hardly usable. I'm not exaggerating.

I agree. it should not be that bad. I've been working during the last couple of days to bring the io usage down. We're much better off than what we were originally. If I cannot reduce it any more then I'll try to throttle it a little bit, that way your system will still be usable.

It seems counter intuitive to me to add an explicit "Disable" button just to counter a bug. Bugs get fixed. Also, you can still disable indexing via the KCM, it's just not completely intuitive.

What do you think?

this makes sense. 

But what is in this scenario: Say you're playing a game or watching a movie on older hardware. If there's no possibility to at least pause the indexer, there will be lags.

(In reply to comment #4)
> this makes sense. 
> 
> But what is in this scenario: Say you're playing a game or watching a movie
> on older hardware. If there's no possibility to at least pause the indexer,
> there will be lags.

Possibly. In that case you really just want to pause it, or tell it to do it later. In the ideal case, the kernel scheduler would prioritize the other processes. We do tell set the niceness level to minimum.

Anyway, the indexing is mostly only visible during the inital phase. After that only modified files are updated. Would it be okay if I closed this bug?

thanks for the work. I'll close the bug. If other users stumble upon this, they may want to reopen this issue.

This is very annoying! My computer is unusable right now, I tried disabling baloo in akonadiconsole but without success. I also tried killing the process, but it keeps reappearing.

I want to use my computer right now, I can do the indexing tomorrow while I'm at work but there is no way of pausing it!

http://askubuntu.com/questions/437635/how-to-turn-off-baloo-in-kde-4-13

I'm fairly surprised that it is consuming so many resources. Would you mind providing some debug info? Could you please tell me which all processes are running which start with baloo? 

$ ps aux | grep baloo

I removed baloo from akonadiconsole, because I had to use my computer. It was using 50% of my memory and my computer was swapping (I have 4GiB of RAM).

Now I added baloo back to akonadiconsole and it finished in a couple of minutes with 1.3% of my memory.

That being said, I think forcing indexing on users is very bad, they should be able to stop it and postpone it in an easy way (akonadiconsole is not meant for normal users). A simple checkbox like we used to have for nepomuk would be nice.

Everytime I log in, baloo makes my computer swap and it becomes unusable. I then kill all of its processes, remove it from akonadiconsole and then add back again. Then it seems to work.