[Bug 1190524] New: baloo keeps my laptop hot
http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 Bug ID: 1190524 Summary: baloo keeps my laptop hot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: saba@sabanet.at QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: Baloo file indexer is running since days at 100% CPU and I'm not sure if it will ever finish. Reproducible: Always Steps to Reproduce: 1. Installed Tumbleweed from scratch on a brand new notebook (LG gram 2021 i7-1165G7) 2. Copied my home directory from my old laptop (approx. 700GB of data) 3. Watch baloo running at 100% CPU for days/weeks Actual Results: Baloo seems to get slower and slower: gram:~> balooctl status ; sleep 3600 ; balooctl status Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 3,683,585 Files waiting for content indexing: 160,364 Files failed to index: 0 Current size of index is 71.48 GiB Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 3,683,065 Files waiting for content indexing: 159,844 Files failed to index: 0 Current size of index is 71.48 GiB This means in one hour the number of files waiting to be indexed decreased only by 520 (which would mean 7 seconds to add a single file to the index). At this speed, I'd need to wait another 300 hours before the indexer completed its job. Expected Results: Indexing should complete *much* faster. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 http://bugzilla.opensuse.org/show_bug.cgi?id=1190524#c1 --- Comment #1 from Christophe Giboudeaux <christophe@krop.fr> --- Check what `balooctl config list includeFolders` and `balooctl config list excludeFolders` returns. Does one location looks like it should not be indexed? What does `balooctl config hidden` return? (This can also be checked in systemsettings / search) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 http://bugzilla.opensuse.org/show_bug.cgi?id=1190524#c2 --- Comment #2 from Rainer Sabelka <saba@sabanet.at> --- "balooctl config list includeFolders" returns just my home directory. "balooctl config list excludeFolders" is empty. "balooctl config hidden" is also empty. Well, I could exclude a lot of subdirectories from being indexed, but unfortunately my directory structure is organized by projects, themes and other criteria, but not by "worth to index or not". While this might be doable it would be quite cumbersome to maintain. And I'd rather prefer to have everything in the index, because when I search for some keyword XYZ and won't find anything, then I can be sure that there is absolutely nothing there containing XYZ and I'm done. Otherwise, I'd think "maybe it's just omitted from the index" and have to search by other means. (e.g. grep -r) Speaking of grep:
time grep -rl something $HOME >out.txt
real 6m59.015s user 2m49.994s sys 1m14.764s So grep can search through my entire home directory in 7 minutes. Yes, I know that indexing takes a lot more than just searching for some bytes - but such a huge difference? Is it possible to find out what baloo is doing and where it spends most of its CPU time? I tried "balooctl monitor": It say "Indexing: /some/files" 40 times, then there is a pause of one and a halve minutes, the come the next 40 files and so on. At the moment is is going throug some html files. I find it hard to believe that, extracting the keywords can take 1,5 minutes for just 40 files, so I'd rather guess that inserting the keywords into the database causes the delay. Maybe a missing index? Anything I can do to identify the bottleneck? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 http://bugzilla.opensuse.org/show_bug.cgi?id=1190524#c3 --- Comment #3 from Rainer Sabelka <saba@sabanet.at> --- Recently I found https://www.reddit.com/r/kde/comments/mebx8f/reminder_to_check_on_your_baloo... and did like suggested in this article balooctl disable balooctl purge balooctl enable The index finished rebuilding over night.
balooctl status Baloo File Indexer is running Indexer state: Idle Total files indexed: 668,289 Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is 7.88 GiB
The index size went down to 1/10 but curiously also the number of files indexed. (The number of files indexed is plausible, a "find $HOME -type f" return ca. 1.000.000 lines). So for me, the problem seems to be fixed. I guess it will be difficult, however, to find the cause of the problem in retrospect. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 http://bugzilla.opensuse.org/show_bug.cgi?id=1190524#c4 --- Comment #4 from Rainer Sabelka <saba@sabanet.at> --- Over the time, baloo's index size and CPU time it consumes, is constantly growing. The underlying problem might be the following bug: https://bugs.kde.org/show_bug.cgi?id=401863 Although this bug report is for btrfs (I'm on ext4) I still think this could be the reason. (May be device IDs change when the kernel or systemd is updated because devices are enumerated differently). The but report above is from 2018, so I'm not expecting any quick progress here. Are there any possible work-arounds (other then deleting and rebuilding the index), or are there alternative indexers available on Tubleweed? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com