Hello,
I’ve noticed that Baloo consumes a significant amount of CPU when I’m compiling large Rust projects. Upon investigating the Baloo source code, it seems there’s currently no support for cache directory tagging—a convention adopted by many tools to mark directories as non-indexable caches.
Would it be possible to add support for this feature in Baloo? It could help reduce unnecessary indexing and improve performance for many development workflows.
Thanks,
Hugues
You can already, exclude folders for the indexation settings.
To my knowledge Cache Directory Tagging Specification – Bryan Ford's Home Page isn’t very widely used, it justly notice there is $XDG_CACHE_HOME that application could use (defaults to ~/.cache), like link from.
Baloo resolves symlink and indexes based on the canonical path, so it would ignore it.
Would it be possible to add support for this feature in Baloo?
Since at least cargo seem to have support fo it built-in that’s already a reason enough to accept this feature.
(baloo source is at Frameworks / Baloo · GitLab github is just a mirror)
- Version 0.4, August 10, 2004: Changed cache tag file name from “
.IsCacheDirectory” to “CACHEDIR.TAG”, to be compatible with old 14-character POSIX file systems and 8.3-character MS-DOS file systems.
This comment in Cache Directory Tagging Specification – Bryan Ford's Home Page is now completey obsolete, .IsCacheDirectory would be much better.
you can choose not to include hidden files at all by unchecking the box, and thus avoid indexing the .cache directory at all.
however if you which it keep the box checked you can add the .cache directory to the list and mark it as Not Indexed, and thus avoid the churn of baloo trying to keep up with your activities.
there is really no reason to index the .cache directory that i can think of.
