https://bugs.kde.org/show_bug.cgi?id=400704
--- Comment #52 from tagwer...@innerjoin.org --- (In reply to postix from comment #48) > ... made my system with an 12-core 5900X and an NVMe drive significantly lag > ... An additional thought here; I've noticed the impact of indexing in a couple of situations: One is when Baloo has hit the limit of memory it is allowed to use. Normally it runs within systemd, with a unit file that sets a 500MB limit on RAM. If Baloo is indexing *a lot*, it may hit that limit and discard (and repeatedly reread) clean pages or start swapping dirty pages. These mean that there is far more IO to the index file and when you start swapping, you are in trouble. You can see what memory is used with a "systemctl status --user kde-baloo" and look at the "Memory" line... Second is if you have deleted a large collection of files - meaning that Baloo has to catch up with removing entries from the index, something that is equivalent to indexing the files in the first place. Both of these come into play if you are content indexing, not really when just indexing filenames/ > > You can see that Baloo stucks most of the time in > `Baloo::PositionDB::get(QByteArray const&)` and > `Baloo::PostingDB::get(QByteArray const&)` called from > `Baloo::WriteTransaction::commit()` -- You are receiving this mail because: You are watching all bug changes.
