https://bugs.kde.org/show_bug.cgi?id=492808
--- Comment #11 from tagwer...@innerjoin.org ---
(In reply to Ellie from comment #10)
> ... So I'm
> not sure this sounds like a changing device id issue ...
Yes, unfortunately. It's quite likely to be.
It's the way Baloo works. It is lightning fast when you do searches because if
it has a word to search for, it looks up where on disk (in the index file) the
list of results are and then pulls up that list as a page. Very little
thinking, very little overhead. However that means when it indexing and it
wants to update the index for that word, if pull up the list of results,
inserts the new filename into the list and writes it back. For each word. You
can imagine what happens for common words, it can be a very big list to read,
update and rewrite.
Of course Baloo knows that this is slightly crazy and does not read and rewrite
the lists for each word and file it indexes - it batches up the indexing into
groups of 40 files, creates a transaction in memory for the 40 and commits. On
top of that it's a memory mapped file which also cuts down on overhead (so the
"reads" are mostly "find the page in memory" and "writes" and "flag this page
as dirty so it will be written back with the commit"). However you can see here
why Baloo is dependent on having enough RAM.
With the BTRFS bug you have a large index (all the results of all the files
with their old ID's), and are indexing the files afresh, pulling up the old
lists, inserting in the new ID's and writing the lists back. At some point the
index will get too large for memory and performance will fall over the edge.
The easy way of seeing if you are heading for trouble is a baloosearch:
$ baloosearch -i one-of-your-files.txt
the "-i" asks for the ID. You should only get a single hit but with the BTRFS
bug you typically get several, the same files (as per the filepath) but
different IDs. You won't see this now as you've deleted the index.
One more "sanity check" would be sensible for your PostmarketOS / BTRFS system;
you would need the
.local/share/baloo
folder that holds the index *not* to be copy on write.
--
You are receiving this mail because:
You are watching all bug changes.
