https://bugs.kde.org/show_bug.cgi?id=437197
--- Comment #8 from Ian Proudler <i.proud...@oxon.org> ---
(In reply to tagwerk19 from comment #6)
> Here's another guess, maybe worth mentioning...
>
> You are doing content indexing - and indexing a lot of data? How big has
> your .local/share/baloo/index file become? What does
>
> balooctl indexSize
>
> say? It could be that baloo is wanting more bits of the database in memory
> than there is memory available. In that case there'll be lots of going back
> and forth to disc. Having a look at your system load (memory, swap) might
> give some clues
Thanks for the suggestion.
I have 8GB RAM. I have conky running on the desktop showing RAM and swap
useage. but I've never noticed baloo causing swap useage. I will take more
notice in future.
balooctl indexSize:
File Size: 2.58 GiB
Used: 1.61 GiB
PostingDB: 495.27 MiB 29.957 %
PositionDB: 886.12 MiB 53.598 %
DocTerms: 257.66 MiB 15.585 %
DocFilenameTerms: 4.32 MiB 0.262 %
DocXattrTerms: 4.00 KiB 0.000 %
IdTree: 744.00 KiB 0.044 %
IdFileName: 3.21 MiB 0.194 %
DocTime: 1.82 MiB 0.110 %
DocData: 2.57 MiB 0.155 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 1.54 MiB 0.093 %
--
You are receiving this mail because:
You are watching all bug changes.
