https://bugs.kde.org/show_bug.cgi?id=476752
--- Comment #2 from Stefan Brüns <stefan.bru...@rwth-aachen.de> --- There is some information missing: 1. Does "5%" refer to one CPU core, or the whole system (i.e 100% on 1 of 20 cores) 2. Is the system currently idle, or are you actively using it? 3. Is this during the initial indexing, or during content indexing? Most indexers are limited to single-threading by the underlying libraries. Although it would be possible to spawn multiple processes, one for each file, this would require some significant changes. If the system has many cores it may be OK to use more than one, preferably efficiency cores if available. But this is definitely something which should be implemented outside of Baloo, so it becomes reusable. There is also the IO throttling happening when the computer is in use (according to KIdleTime). Currently the throttling is fairly aggressive and could probably be relaxed. But pushing this up too much will result complains, flame wars etc. And "too much" is highly system dependent. -- You are receiving this mail because: You are watching all bug changes.
