https://bugs.kde.org/show_bug.cgi?id=400704
Bug ID: 400704
Summary: Baloo indexing I/O introduces serious noticable delays
Product: frameworks-baloo
Version: 5.45.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: axel.br...@gmx.de
Target Milestone: ---
As suggested in https://bugs.kde.org/show_bug.cgi?id=333655#c73 , lets open a
new bug for baloo 5:
I'm running baloo 5.45.0 on openSUSE Leap 15, and notice that my complete
desktop freezes regularly for 1-2 minutes(!). CPU monitor reports during that
time 100% Load on both cores, but top does not show any process of a
considerable CU load. The problem is more the couple of baloo and akonadi, as
iotop shows:
Total DISK READ : 10.37 M/s | Total DISK WRITE : 1060.53 K/s
Actual DISK READ: 10.37 M/s | Actual DISK WRITE: 197.36 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
4497 idle axel 9.73 M/s 0.00 B/s 0.00 % 99.52 %
baloo_file_extractor
2847 idle axel 651.54 K/s 1058.15 K/s 0.00 % 97.97 %
akonadi_indexing_agent --identifier akonadi_indexing_agent
23 be/4 root 0.00 B/s 0.00 B/s 0.00 % 0.10 % [kworker/1:1]
2479 be/4 axel 0.00 B/s 0.00 B/s 0.00 % 0.08 % plasmashell
849 be/4 root 4.76 K/s 0.00 B/s 0.00 % 0.00 % [xfsaild/sda2]
(interesting percentage calculation of iotop by the way)
System disk is a SSD, data disk is a hybrid 1TB disk with 8G cache.
I have configured the search to not index the file content. Thats why the heavy
IO surprises me even more
--
You are receiving this mail because:
You are watching all bug changes.
