https://bugs.kde.org/show_bug.cgi?id=502641
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagwer...@innerjoin.org
--- Comment #1 from tagwer...@innerjoin.org ---
(In reply to peer.griebel from comment #0)
> 1. restart baloo (systemctl --user restart kde-baloo.service)
> 2. balooctl6 status reports (very fast) that 27 files have still to be
> examined
> 3. balooctl6 monitor shows that some files get indexed
> 4. balooctl6 status takes very long time to answer
> 5. repeat whole process, yields same result
> ....
> ADDITIONAL INFORMATION
> The list of files which are reported by balooctl6 monitor does not help:
> Even if I remove the last files in this list, baloo stops working on some
> file further to the front of the list.
I've not seen exactly that behaviour but something close. When running Baloo
under systemd it is limited to using 512 MB RAM. You can see the memory use
with
$ systemctl --user status kde-baloo
Look for a "Memory:" line.
If are indexing a lot of files, Baloo might be fighting to work within the
constraints. Initially, you see the impact as Baloo reads and drops, rereads
and drops pages from the database - it has to drop pages it has read in order
to read others.
If Baloo is content indexing and building a large transaction, it will not be
able to "drop" those pages, it will have to ask for more memory. When reaching
the 512MB limit, there'll be a gradually increasing delay in allocating it.
Potentially Baloo will start swapping, which is bad news...
If this it the problem, a potential "quick fix" is to allow Baloo more RAM,
try 25% rather than a fixed 512MB.
$ systemctl --user edit kde-baloo
and add the lines to the "override" file (this change is just for your logged
on user):
[Service]
MemoryHigh=25%
and restart:
$ systemctl --user restart kde-baloo
> I would like to debug this problem but I do not know how.
If you want to check to see whether Baloo is hitting the limits, you can use
iotop and see whether Baloo has started to read and reread pages
and whether the CPU use is dropping as a result of the delays in allocating
more memory.
An alternative is to manually index the remaining files individually with
"balooctl6 index ....", that indexing is done in the foreground and without the
systemd limits on RAM usage. Maybe this will give error messages for files...
Good luck and lets us know how the tests went...
--
You are receiving this mail because:
You are watching all bug changes.
