https://bugs.kde.org/show_bug.cgi?id=404057
Martin Steigerwald <mar...@lichtvoll.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Uses an insane amount of |Uses an insane amount of
|memory (RSS/PSS) and writes |memory (RSS/PSS) writing a
|a *ton* of data while |*ton* of data while
|indexing |re-indexing unchanged files
--- Comment #30 from Martin Steigerwald <mar...@lichtvoll.de> ---
(In reply to Kai Krakow from comment #28)
> (In reply to Kai Krakow from comment #19)
[…]
> Following up with more details:
>
> The problem seems to be the following:
>
> After reboot, the indexer finds all files as changed. For every file in the
> index, it will log to stdout/stderr:
>
> "path to file" id seems to have changed. Perhaps baloo was not running, and
> this file was deleted + re-created
Kai, please see my comment #2 of this bug report:
https://bugs.kde.org/show_bug.cgi?id=404057#c2
I got exactly the same message. Just have been rereading what I wrote as I have
not been aware of it anymore.
So yes, that is indeed an important issue here. I believe this bug is at least
about two or three independent issues, but as you told, let's have it about the
re-indexing files thing. I bet getting rid of needlessly re-indexing files will
be one of the most effective to sort out performance issues with Baloo. I
changed bug subject accordingly.
--
You are receiving this mail because:
You are watching all bug changes.
