[opensuse-factory] Machine seems sluggish, under KDE,, local access is slow and baloo_file takes 15-20% of the cores
Hello all: I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings top - 15:16:39 up 6:13, 2 users, load average: 4.42, 4.61, 4.42 Tasks: 249 total, 5 running, 244 sleeping, 0 stopped, 0 zombie %Cpu(s): 20.5 us, 6.6 sy, 10.7 ni, 53.0 id, 9.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 16313284 total, 6434336 free, 3929372 used, 5949576 buff/cache KiB Swap: 2106364 total, 2106364 free, 0 used. 11708652 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2073 FoolishEwe 39 19 0.251t 105068 35572 R 100.0 0.644 371:21.98 baloo_file_extr 5240 FoolishEwe 20 0 0.251t 75876 41084 R 100.0 0.465 247:31.95 baloorunner 3566 FoolishEwe 20 0 2866320 804668 135276 R 31.46 4.933 14:04.69 Web Content 1755 FoolishEwe 20 0 3382192 147968 93032 S 20.86 0.907 64:49.36 kwin_x11 1498 root 20 0 796768 389536 326608 S 12.58 2.388 40:22.39 X 1759 FoolishEwe 20 0 5375096 364092 185416 S 8.278 2.232 31:47.82 plasmashell 2968 FoolishEwe 20 0 2853168 690396 199060 R 8.278 4.232 23:50.19 Web Content 5052 FoolishEwe 20 0 1772076 205224 106588 S 7.947 1.258 16:04.77 ksysguard 1783 FoolishEwe 9 -11 2742024 14856 11360 S 4.967 0.091 0:36.95 pulseaudio 1811 FoolishEwe 20 0 718664 111640 80288 S 4.305 0.684 0:26.37 konsole 1864 FoolishEwe 20 0 3359864 742824 266208 S 2.318 4.553 40:32.54 firefox 5058 FoolishEwe 20 0 10284 2296 2016 S 1.656 0.014 4:02.54 ksysguardd 1107 root 20 0 49884 6096 5156 S 1.325 0.037 0:55.81 bluetoothd 12225 root 20 0 0 0 0 S 0.662 0.000 0:00.68 kworker/u16:3 12313 FoolishEwe 20 0 41304 4108 3496 R 0.662 0.025 0:00.14 top 644 root 20 0 12140 5064 1584 S 0.331 0.031 0:10.17 haveged 1084 root 20 0 55452 5760 4948 S 0.331 0.035 0:06.20 systemd-logind 2088 FoolishEwe 20 0 2559384 440980 126848 S 0.331 2.703 12:20.68 Web Content 5613 FoolishEwe 20 0 994812 214216 93496 S 0.331 1.313 0:14.53 okular 12076 root 0 -20 0 0 0 S 0.331 0.000 0:00.26 kworker/u17:0 1 root 20 0 218112 9232 6720 S 0.000 0.057 0:07.12 systemd
w 15:06:34 up 6:03, 2 users, load average: 4.29, 4.29, 4.19 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT FoolishEwe pts/0 :0 09:05 6:01m 0.15s 0.15s /bin/bash FoolishEwe pts/0 :0 09:05 6:01m 0.15s 0.15s /bin/bash FoolishEwe pts/1 :0 09:05 2.00s 1:50 0.00s w FoolishEwe pts/1 :0 09:05 2.00s 1:50 0.00s w
With best regards: Bill N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
On 2017-11-21 00:26, Foolish Ewe wrote:
Hello all:
I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings
Baloo is an indexer, and for some reason it may be stuck, loading the hard disk heavily and thus slowing your machine as a result. Maybe you need to kill it and erase its index. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [11-20-17 19:35]:
On 2017-11-21 00:26, Foolish Ewe wrote:
Hello all:
I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings
Baloo is an indexer, and for some reason it may be stuck, loading the hard disk heavily and thus slowing your machine as a result.
Maybe you need to kill it and erase its index.
but, beware that erasing the index means that baloo must regenerate that index and will be more "cpu intensive" until that is accomplished. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-11-20 a las 21:38 -0500, Patrick Shanahan escribió:
* Carlos E. R. <> [11-20-17 19:35]:
On 2017-11-21 00:26, Foolish Ewe wrote:
Hello all:
I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings
Baloo is an indexer, and for some reason it may be stuck, loading the hard disk heavily and thus slowing your machine as a result.
Maybe you need to kill it and erase its index.
but, beware that erasing the index means that baloo must regenerate that index and will be more "cpu intensive" until that is accomplished.
True. But I'm thinking of a corrupt index. I remember indexers getting hung on a particular file and never finish. Or maybe the matter to index is huge :-? I'm not familiar with current KDE/Plasma whatever, but surely the indexing can be configured somewhere. - -- Cheers Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAloTl/AACgkQja8UbcUWM1y2zAEAk1cwIVZnzej7YGjepBY+BjFH P8fk/jUv/g7OpGMuIC8A/3hVyewNWMH6HiAZuCj2tF6BlYD1hvygTAJBWbqU/yOd =5wm5 -----END PGP SIGNATURE-----
* Carlos E. R. <robin.listas@telefonica.net> [11-20-17 22:06]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2017-11-20 a las 21:38 -0500, Patrick Shanahan escribió:
* Carlos E. R. <> [11-20-17 19:35]:
On 2017-11-21 00:26, Foolish Ewe wrote:
Hello all:
I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings
Baloo is an indexer, and for some reason it may be stuck, loading the hard disk heavily and thus slowing your machine as a result.
Maybe you need to kill it and erase its index.
but, beware that erasing the index means that baloo must regenerate that index and will be more "cpu intensive" until that is accomplished.
True. But I'm thinking of a corrupt index. I remember indexers getting hung on a particular file and never finish.
Or maybe the matter to index is huge :-?
I'm not familiar with current KDE/Plasma whatever, but surely the indexing can be configured somewhere.
yes, there are: balooctl baloo_file_extractor baloosearch baloo_file baloo_filemetadata_temp_extractor balooshow and most have <cmd> --help explanations and systemsettings5 contains a "search" configuration -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 21/11/17 06:24, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [11-20-17 22:06]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2017-11-20 a las 21:38 -0500, Patrick Shanahan escribió:
* Carlos E. R. <> [11-20-17 19:35]:
On 2017-11-21 00:26, Foolish Ewe wrote:
Hello all:
I'm running on what should be a nearly idle machine with fast hardware, but it doesn't feel like it. My laptop has a high constant load average and becomes unresponsive. I think I'm running with default settings for this service, what would be the appropriate settings
Baloo is an indexer, and for some reason it may be stuck, loading the hard disk heavily and thus slowing your machine as a result.
Maybe you need to kill it and erase its index.
but, beware that erasing the index means that baloo must regenerate that index and will be more "cpu intensive" until that is accomplished.
True. But I'm thinking of a corrupt index. I remember indexers getting hung on a particular file and never finish.
Or maybe the matter to index is huge :-?
I'm not familiar with current KDE/Plasma whatever, but surely the indexing can be configured somewhere.
yes, there are: balooctl baloo_file_extractor baloosearch baloo_file baloo_filemetadata_temp_extractor balooshow
and most have <cmd> --help explanations
and systemsettings5 contains a "search" configuration
Instead of killing baloo, it might be useful to run: balooctl monitor to check what it's doing. And if that's not enough, there's documentation on: https://community.kde.org/Baloo/Configuration For example, this might be useful if you want to exclude a git directory with many files: https://community.kde.org/Baloo/Configuration#Exclude_Folders. or just running: balooctl config add excludeFolders /home/antonio/tmp/ Also, 'balooctl config list' shows the configuration options. Hope that helps. -- Antonio Larrosa -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Antonio Larrosa -
Carlos E. R. -
Foolish Ewe -
Patrick Shanahan