https://bugs.kde.org/show_bug.cgi?id=380456
Michael Heidelbach <ottw...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ottw...@gmail.com
--- Comment #3 from Michael Heidelbach <ottw...@gmail.com> ---
(In reply to Gaël de Chalendar (aka Kleag) from comment #0)
> 1. Install KDE Neon on a machine with several thousand files, for example a
> development machine
baloo is having a hard time indexing plain text, because there are so many
terms to extract. Also the backend database is memory based so I would expect
memory consumption to rise during the process.
Please report memory usage when indexing is done. I'm really curious to see
that.
> Baloo File Indexer is running
> Indexer state: Inactif
> Indexed 361894 / 1513487 files
This is strange: There are a lot of files left to be indexed, but the indexer
itself is idle?
Did you kill it? Probably not. I've encountered this many times.
Anyway this behaviour definitely is worth scrutinizing. I'll do it when I'm
more familiar with baloo's code.
For the time being, occasionally it helps to restart baloo with
$ balooctl stop
ensure baloo_file and baloo_file_extractor are not running
$ balooctl start
> Current size of index is 6,28 Gio
With an index of that size searching might be a little slow. And your even
half-way done :)
Not sure, but I have the feeling baloo wasn't designed for this and you're
overburdening it.
I'm just trying to imagine what will happen when you enter 'const' in
KRunner/Milou.
--
You are receiving this mail because:
You are watching all bug changes.
