https://bugs.kde.org/show_bug.cgi?id=488446
--- Comment #20 from tagwer...@innerjoin.org ---
(In reply to contact from comment #16)
> (In reply to tagwerk19 from comment #4)
> > ... if you search for a file you know you've indexed (with baloosearch -i
> > one-of-your-files"), do you get just a single or multiple results?
>
> Okay, a lot of files I tried to find simply have not been indexed yet. But I
> have found a bunch of files with multiple indexes now.
In that case, it's probably best to kill the indexing, remove the index
("balooctl purge") and restart...
... But before you do that
(In reply to contact from comment #18)
> This however is a small extract of the output I get from .obj files:
>
> 968788 968789 96879 968790 968791 968792 968793 968794 968795 968796 968797
> 968798 968799 9688 96880 968800 968801 968802 968803 968804 968805 968806
> 968807 968808 968809 96881 968810 968811 968812 968813 968814 968815 968816
> ...
Probably not a lot of point indexing that and it's definitely hammering the
index.
Summarising https://bugs.kde.org/show_bug.cgi?id=488533#c1
> ... Baloo can exclude mime types. Edit your ~/.config/baloofilerc and add a
> line under [General]:
>
> exclude mimetypes=model/obj
>
> or with a command:
>
> balooctl config add excludeMimetypes model/obj
>
> This seems to let baloo index the filename but not index the content ...
If you do this, it should stop Baloo content indexing the .obj files, you can
then kill Baloo, purge the index with "balooctl purge" and start again. You
should find it indexes faster, because of the extra memory and because you've
got rid of all the old duplicates. It might still take a while with the amount
of data you have but you can watch progress with "balooctl monitor"
We probably need to exclude "model/obj" files by default
Hope this makes sense and good luck!
--
You are receiving this mail because:
You are watching all bug changes.
