https://bugs.kde.org/show_bug.cgi?id=487916
--- Comment #12 from tagwer...@innerjoin.org --- (In reply to Vyacheslav Kovalevsky from comment #11) > ... Sorry but this is awful ... As above, we really need to know what's happening with the memory (and the memory limits) in order to sort these issues. Seize-up's of a system because of Baloo is normally because it is *not* constrained by the systemd unit files, on a big and busy system it will be trying to catch up and *can* squeeze out foreground tasks. What was, of old, complained about as "hogging the CPU" was most likely fighting for RAM. With the systemd cap, use "systemctl status --user kde-baloo" to check, Baloo will live in its small jail. It might have trouble working within 512 MB but that would impact I/O reads from the index file and potentially swap if indexing new/changed files. You can adjust the space you give it. It's a balancing act. In reality, if you are doing sort of work you are doing, it's best to just index the filenames (and not filenames and content) and exclude your immediate workspace - where you are creating, modifying, deleting lots and appending to large log files. If you look and see that Baloo is spending a disproportionate amound of time on some filetypes, let us know, maybe they are worth an exclusion. -- You are receiving this mail because: You are watching all bug changes.
