https://bugs.kde.org/show_bug.cgi?id=487916
--- Comment #5 from tagwer...@innerjoin.org ---
(In reply to Sergio from comment #4)
> ... The first time it was huge, after that first time it is about 5-10' ...
5 to 10 minutes (for baloo_file, not the heavier baloo_file_extractor) is way
more than expected...
It would be sensible to see whether you've indexed multiple copies of your
files (a hang over from the earlier problems with BTRFS), see if
baloosearch -i one-of-your-files.txt
give a single or multiple hits - where the '-i' lists the internal "Document
ID" that Baloo uses. If you get multiple hits, it would make sense to purge the
index and leave Baloo reindexing from scratch (when you have time!). Possible
that there are issues with BTRFS snapshots, make sure that you have the
snapshot directories excluded.
I remember someone posting that during the initial indexing, they placed the
index on /tmp (possibly in RAM). That would avoid contention on the disk. Of
course, this is the initial indexing not the scan done when you log on. Putting
a symlink in at
.local/shared/baloo
to a different location seems to work (but likely not recommended 8-). Beyond
that, I'm running out of ideas..
--
You are receiving this mail because:
You are watching all bug changes.
