[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 --- Comment #7 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 --- Comment #6 from [email protected] --- (In reply to tagwerk19 from comment #4) > (In reply to Henning from comment #2) > > I only scan home, and excluded a lot of directories that contain junk, like > > archives etc. > Hidden Files and Folders? > > Best exclude .cache, .local/share/Trash, .mozilla and .thunderbird (of you > have them). I wonder if Kinoite makes a lot of use of .var/apps, try > excluding that as well. Did you try these exclusions? If you indexing hidden files/folder, make sure .cache is excluded at a minimum... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 [email protected] changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from [email protected] --- There's a patch to the unit file to set the MemoryHigh limit to 25% (instead of the harsh 512MB), released as part of KDE Frameworks 6.26.0 https://kde.org/announcements/frameworks/6/6.26.0/ There have also been changes that should avoid the index being locked when extracting the plain text from large files/pdf's, if the index is locked new info is appended. That means the indexing can continue but the index can jump in size. No guarantees but maybe these changes can help. If you are still having trouble, append a reply :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 --- Comment #4 from [email protected] --- (In reply to Henning from comment #2) > Fedora 41 Kinoite... Ooo. New territory... > I only scan home, and excluded a lot of directories that contain junk, like > archives etc. Hidden Files and Folders? Best exclude .cache, .local/share/Trash, .mozilla and .thunderbird (of you have them). I wonder if Kinoite makes a lot of use of .var/apps, try excluding that as well. > ... I had severe performance issues and the index was pretty big. That was a > problem in the past too, high CPU load ... You can try "systemctl status --user kde-baloo". That should include a "Memory:" line showing how much memory Baloo is allowed, Nowadays it is capped at 512MB and there have been bugs where that was too small. When it is too small, Baloo has to work a lot harder to sort and clear memory, reread pages back from the index. It really is a balancing act, you don't want Baloo affecting performance by taking too much RAM and you don't want is fighting to work in too small a space. Oooo, and you really don't want it swapping, that really affects you. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 Méven changed: What|Removed |Added CC||[email protected] Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Méven --- (In reply to Henning from comment #2) > Fedora 41 Kinoite, default BTRFS stuff, no /home snapshots > > I only scan home, and excluded a lot of directories that contain junk, like > archives etc. > > I dont always use these default directories, instead I scanned my entire > home and excluded a lot. > > In the end the issue is not the amount of files, but the huge index file. > Scanning some directories including file content, but by default only names, > would be better for most users I think. > > I had severe performance issues and the index was pretty big. That was a > problem in the past too, high CPU load. Can you share the result of the commands: balooctl6 status balooctl6 failed After an index purge you can monitor baloo using `balooctl6 monitor`. The issue is likely a file that causes baloo to misbehave, identify the files and sharing them would be very helpful. Then if you can/want to use heaptrack (https://github.com/KDE/heaptrack) or gdb to actually diagnose the issue, we can help. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 --- Comment #2 from Henning --- Fedora 41 Kinoite, default BTRFS stuff, no /home snapshots I only scan home, and excluded a lot of directories that contain junk, like archives etc. I dont always use these default directories, instead I scanned my entire home and excluded a lot. In the end the issue is not the amount of files, but the huge index file. Scanning some directories including file content, but by default only names, would be better for most users I think. I had severe performance issues and the index was pretty big. That was a problem in the past too, high CPU load. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 502086] Defaulting to "scan file content" causes huge CPU load and index filesize
https://bugs.kde.org/show_bug.cgi?id=502086 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #1 from [email protected] --- What's the version of Fedora? Presumably you've got BTRFS disks but anything you think might be "out of the ordinary"? Maybe BTRFS snapshots? Have you stuck with Fedora defaults of indexing ~/Documents, ~/Music, ~/Pictures and ~/Videos? -- You are receiving this mail because: You are watching all bug changes.
