https://bugs.kde.org/show_bug.cgi?id=400704
Oded Arbel <o...@geek.co.il> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |o...@geek.co.il
--- Comment #29 from Oded Arbel <o...@geek.co.il> ---
Same problem here - Baloo eats up all IO even when reporting "idle". This has
become a problem only in the last year or so. I'm using a pretty beefy i7
device with an NVME and while Baloo is enabled the computer often is slow and
freezes from time to time. Looking at CPU usage I see `baloo_file` takes
50%~80% CPU, and loadavg is around 3~4.5 (on 4 core system).
Looking at IO:
---8<---
$ pidstat -G balo[o] -dl 5 1; balooctl status
Linux 5.4.0-17-generic (vesho) 03/20/2020 _x86_64_ (8 CPU)
12:48:52 AM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
12:48:57 AM 1000 80482 26164.94 64858.96 0.00 170
/usr/bin/baloo_file
Average: UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
Average: 1000 80482 26164.94 64858.96 0.00 170
/usr/bin/baloo_file
Baloo File Indexer is running
Indexer state: Idle
Total files indexed: 297,288
Files waiting for content indexing: 0
Files failed to index: 0
Current size of index is 2.56 GiB
----8<----
So balooctl reports "Idle" while baloo_file pushes >60Mbit/sec to the drive and
does not insignificant reading.
In .xsession-errors log I can see a lot of messages like this:
----8<----
org.kde.baloo.engine: DocumentDB::get 307907124573241397 MDB_NOTFOUND: No
matching key/data pair found
----8<----
--
You are receiving this mail because:
You are watching all bug changes.
