| Summary: | baloo_file_extractor uses a significant amount of system resources; balooctl6 monitor simply shows ": Ok" | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | A. D. Cramer <alexcramer> |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | tagwerk19 |
| Priority: | NOR | ||
| Version First Reported In: | 6.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
A. D. Cramer
2025-01-19 06:10:10 UTC
(In reply to A. D. Cramer from comment #0) > 1. Copy the entire /home directory to a folder on a different drive. > 2. Make the main partition on that drive mount as /home, moving some > directories around to make this feasible You are reindexing everything... If you've copied to a different drive the files will have a different FilesystemID/inode and Baloo will consider them "new". > Here is the output of balooctl6 status: > Baloo File Indexer is running > Indexer state: Indexing file content > Total files indexed: 5,551,335 > Files waiting for content indexing: 1,568,892 You've got a lot of files, Baloo is working through them. All the same, it would be best to delete the index and start again (pkill baloo_file; balooctl6 purge), Baloo is remembering everything it indexed on its "old" disc. You don't need that and it will make the indexing slower and more disk and RAM intensive. The index file itself if pretty large... > ...and balooctl6 running for one minute > Press ctrl+c to stop monitoring > File indexer is running > Indexing file content > : Ok > - 358 repeating lines removed for brevity - > : Ok > ^C Could be you've got loads of code in your $HOME. The monitor is not so good at telling the Baloo has looked at a file and decided it's on the mimetype exclusion list. (In reply to tagwerk19 from comment #1) > ... it would be best to delete the index and start again ... Did you have any luck here? > ... Could be you've got loads of code in your $HOME ... It would be interesting to know... C, C++ code or whatever. You can get a list of the mimetype exclusions with: balooctl6 config list excludeMimetypes | sort (In reply to tagwerk19 from comment #2) > (In reply to tagwerk19 from comment #1) > > ... it would be best to delete the index and start again ... > Did you have any luck here? > > > ... Could be you've got loads of code in your $HOME ... > It would be interesting to know... C, C++ code or whatever. > > You can get a list of the mimetype exclusions with: > balooctl6 config list excludeMimetypes | sort Apologies about the late reply, I have been quite busy for the last few days. Deleting the index did help quite a bit, there are now 1 million less files in the index and only 300 thousand waiting for indexing. I have quite a few Git repos in ~/git, along with quite a few on a drive specifically for them, so that may be what code is in $HOME. Most of it is Java, however there is also a rather substantial amount of C in there as well, along with some Python, CSS, and PHP. Memory usage is still quite high (now surpassing 1GiB), however drive usage has gone down quite a bit, and the system is no longer slowing down because of it. I think the main bug here may just be the ambiguous logging of excluded mimetypes in the monitor. 🐛🧹 ⚠️ 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! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |