https://bugs.kde.org/show_bug.cgi?id=487916
--- Comment #4 from Sergio <sergio.calleg...@gmail.com> --- > If you reboot now, has baloo_file done its work or does it still take time? I see the issue every time I restart the system. For sure when I reboot, most likely (I'll check again) even when I logout and login again. Baloo_file hogs the machine for some time. The first time it was huge, after that first time it is about 5-10'. > You can adjust the amount of RAM with > systemctl --user edit kde-baloo > and you can change the "MemoryHigh=512M" to something like "MemoryHigh=25%", > that will give Baloo more breathing room but not allow it to starve other > processes of memory. The 512MB might be too tight. I can try that, but baloo does not seem to be under memory pressure. My set of indexed files is actually not that big. Furthermore, systemd always reports a memory usage well below the limit (`Memory: 249.1M (high: 512.0M available: 262.8M peak: 249.2M)`). > These work "by asking" Baloo to stop rather than killing it. If Baloo is busy > it does not always listen :-/ Even when busy, baloo should probably try to be a better listener ;-). The issue is that right after boot things like giving a presentation are sort of impossible unless you kill `baloo_file` the hard way, which is not really nice. -- You are receiving this mail because: You are watching all bug changes.
