poboiko added a comment.
In D21440#471144 <https://phabricator.kde.org/D21440#471144>, @broulik wrote: > The idle tracking is only in the extractor process, not in baloo_file itself. On startup it runs the `UnindexedFileIndexer` and iterates all the folders looking for files to re-index, consuming a considerable amount of CPU time, spending most of its time doing regexp matching, mime type determination, and date time processing. Only after that it may run the extractor process when there's new files to be indexed. > So I think starting `baloo_file` later is safe since it checks all the files anyway? Otherwise/additionally, we should look into making the `UnindexedFileIndexer` start delayed. I think it should be pretty safe to start `baloo_file` later. The very reason to add `UnindexedFileIndexer` was to make sure we index those files which were changed/added when Baloo wasn't running (as well as `IndexCleaner` to take care of files which were removed). REPOSITORY R293 Baloo REVISION DETAIL https://phabricator.kde.org/D21440 To: broulik, bruns, #baloo, davidedmundson Cc: poboiko, kde-frameworks-devel, gennad, domson, ashaposhnikov, michaelh, astippich, spoorun, ngraham, bruns, abrahams
