https://bugs.kde.org/show_bug.cgi?id=461256
--- Comment #7 from tagwer...@innerjoin.org --- (In reply to Alberto Salvia Novella from comment #0) > If you create many files at the same time, like you do when compiling > software, that makes baloo to noticeably slow the system down. >From what I've seen, you are most likely to notice the impact of baloo when it is greedy with RAM. Looking at the options... You can check how much CPU the "baloo_file" process is using if you look with "top" or "htop". You should see that has priority 39 (maybe listed as "nice" 19), baloo should then yield to anything else wanting to do work. You may see that it still takes 100% of a CPU, but it's using the CPU only when other processes don't need it. If baloo_file is not running with this "idle" priority, then something is wrong. If you see "baloo_file" repeated reappear with different process numbers, then it could be crashing and handling the crash is eating the resources. If you are watching with "htop", you'll also see how much memory baloo_file is using. Shouldn't really be more than 60% (if it is more, the system might be thinking of swapping or about OOM killing the process). Neither are good... You can watch the I/O load with "iotop" (need to run this as root). You can get iotop to display the total (accumulated) writes as baloo_file writes (and commits) data to the index. If you see the "total writes" adding up to significantly more than the size of the index, then something else is wrong. (In reply to Alberto Salvia Novella from comment #2) > ... if I enable Baloo again, the resulting index is: > > $ balooctl indexSize > File Size: 141,81 MiB > Used: 137,87 MiB So it doesn't look as if the index is large enough that even if all pages were in memory, it would cause a problem... (In reply to Alberto Salvia Novella from comment #4) > The initial indexing of baloo slows things more, than creating 500000 files > recursively itself. 500000 files is "substantial", 50000 should be noticeable but not painful. You should be able to repeat tests with creating the files and watching what's happening with htop/iotop. (In reply to Alberto Salvia Novella from comment #6) > Compilation usually involves creating and deleting files. I asked about file deletions as deletions seem to load baloo far more than file creations. Sometimes better to "balooctl purge" and let the index rebuild than wait for baloo to delete many thousand files. Bug 437754 can be used in evidence of this... You might find baloo trying to keep up with all the temp files created and deleted, if you are regularly building/rebuilding software you might think of excluding your working directory from indexing. That said, if baloo is not content indexing, you should scarcely notice it running. -- You are receiving this mail because: You are watching all bug changes.
