[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 --- Comment #7 from marcus --- Created attachment 163009 --> https://bugs.kde.org/attachment.cgi?id=163009&action=edit System load during IDLE indexing So this is the ~5% cpu load visualized. It is core 5 and 6 that do stuff the rest is idle -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 marcus changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from marcus --- Status changed back to reported. I hope this is correct -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 --- Comment #5 from marcus --- I use stock hardware This is copied from system settings. Sorry for language mix. > Betriebssystem: Manjaro Linux > KDE-Plasma-Version: 5.27.9 > KDE-Frameworks-Version: 5.111.0 > Qt-Version: 5.15.11 > Kernel-Version: 6.1.60-1-MANJARO (64-bit) > Grafik-Plattform: X11 > Prozessoren: 16 × 11th Gen Intel® Core™ i7-11700F @ 2.50GHz > Speicher: 15,5 GiB Arbeitsspeicher > Grafikprozessor: NVIDIA GeForce RTX 3060/PCIe/SSE2 > Hersteller: Acer > Produktname: Predator PO3-630 > Systemversion: 1.0 Yesterday I startet a Manjaro system update which might have triggered reindexing. I just don't know. The system was in IDLE state when I noticed the fan going up and down. In KDE Systemmonitor I could see one CPU thread being active while others were inactive which led to ~5% CPU usage. Please let me know if more information is missing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #4 from [email protected] --- (In reply to Stefan Brüns from comment #2) > There is also the IO throttling happening when the computer is in use > (according to KIdleTime). My experience is that when baloo thinks the system is not busy and says kf.baloo: Not busy, fast indexing you can use a full CPU core. As soon as you ask the system to do "anything", baloo switches to kf.baloo: Busy, paced indexing and you get a noticeable pause after indexing each batch of 40 files. (This is with content indexing...) > ... pushing this up too much will result complains, flame wars etc. And "too > much" is highly system dependent ... If you have a "turbo" button, you are not changing the defaults, it's then a user choice and you can ignore the flame wars :-) Maybe increase the number of files indexed per batch. Maybe switch to "fast indexing". Maybe increase the "MemoryHigh" in the systemd unit file. I think it's a useful option... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 Stefan Brüns changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Stefan Brüns --- information required -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 --- Comment #2 from Stefan Brüns --- 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.
[frameworks-baloo] [Bug 476752] Option to un-throttle Baloo File Indexing Process
https://bugs.kde.org/show_bug.cgi?id=476752 Nate Graham changed: What|Removed |Added CC||[email protected], ||[email protected] ||e Summary|Priorize Baloo File |Option to un-throttle Baloo |Indexing Process|File Indexing Process --- Comment #1 from Nate Graham --- Funny, this is usually the opposite of what people ask for. :) I'm not sure it makes that much sense to add a user-facing knob for some kind of "turbo mode", but I wouldn't argue strongly against it either. What do you think, Stefan? -- You are receiving this mail because: You are watching all bug changes.
