https://bugs.kde.org/show_bug.cgi?id=400704
rich...@meinsen.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rich...@meinsen.net
--- Comment #23 from rich...@meinsen.net ---
currently after system start and sometimes during work baloo grabs one cpu for
100% for quite a while, eats up to 13GB ram and makes the system quite
unresponsive (i7 w 4c+ht, 20gb ram, only ssd) when running.
this looks more like a complete reindexing of everything on the system and not
related to the amount of changed files. and i don't see how I could find what
exactly baloo is working on through means of balooctl.
i use fedora 29 with standard schedulers. baloo taking 100% of cpu seems not
reasonable to me. also taking up to 13GB ram seems not reasonable to me.
during the last long run baloo status stated
130470/133866 files index and current index size 15,61 GiB. there was no change
of more than 3000 large files since the last baloo 100% cpu run. indexing of a
new 185m git clone should have be done in very few minutes max.
Further the numbers in indexSize look strange to me
Actual Size: 15,61 GiB
Expected Size: 9,16 GiB
PostingDB: 1,40 GiB 120.956 %
PositionDB: 133,54 MiB 11.266 %
DocTerms: 877,32 MiB 74.014 %
DocFilenameTerms: 13,61 MiB 1.148 %
DocXattrTerms: 0 B 0.000 %
IdTree: 2,52 MiB 0.213 %
IdFileName: 10,07 MiB 0.850 %
DocTime: 5,64 MiB 0.476 %
DocData: 6,92 MiB 0.584 %
ContentIndexingDB: 0 B 0.000 %
FailedIdsDB: 0 B 0.000 %
MTimeDB: 2,18 MiB 0.184 %
Why is the expected size only 2/3 of actual?
And why don't the DB sizes sum up to the actual size?
And what does 120% really mean?
--
You are receiving this mail because:
You are watching all bug changes.
