https://bugs.kde.org/show_bug.cgi?id=500665
--- Comment #44 from postix <pos...@posteo.eu> --- So, I let the system run and index for an hour: it uses now 8.3 GB RES RAM and 100% CPU, the fan is spinning, but in the moment it lags much less. Not sure if I should call it resolved as it had lagged shortly after starting the indexing? ------- > balooctl indexSize File Size: 61.38 GiB Used: 2.92 GiB PostingDB: 3.79 GiB 129.721 % PositionDB: 410.92 MiB 13.728 % DocTerms: 1.52 GiB 52.108 % DocFilenameTerms: 327.26 MiB 10.933 % DocXattrTerms: 4.00 KiB 0.000 % IdTree: 69.90 MiB 2.335 % IdFileName: 373.34 MiB 12.472 % DocTime: 188.30 MiB 6.291 % DocData: 179.93 MiB 6.011 % ContentIndexingDB: 34.50 MiB 1.153 % FailedIdsDB: 0 B 0.000 % MTimeDB: 62.39 MiB 2.084 % -- You are receiving this mail because: You are watching all bug changes.
