Bug#804387: ksysguard: hogs bandwidth if system load results displayed using a thin client
Package: ksysguard
Version: 4:4.11.13-2
Severity: normal
Dear Maintainer,
If I run ksysguard (a.k.a system monitor) directly on my fast box with
KDE desktop it takes very little bandwidth, but if I display that KDE
desktop (including the system monitor GUI) running on the fast box
using a thin client (X-terminal) then ksysguard hogs a lot of LAN
bandwidth (typically 20 MiB/s sent from the fast box to the thin
client on eth1 in this case which corresponds to my LAN). For gigabit
ethernet LAN (my current case) this is not a severe issue, but
that amount of traffic would certainly swamp a 100Megabit LAN.
I have attached a screenshot showing the combined nethogs and system
monitor (a.k.a. ksysguard) results for the thin-client case which
demonstrates the large bandwidth being consumed when the "system load"
is being displayed. If you stop that active "system load" display by
iconifying the GUI, switching to "process table" or switching to a
different KDE desktop the bandwidth consumption drops to near zero.
Furthermore, if I change from default 0.5 seconds time resolution for
the "system load" tab to 1 second, the bandwidth consumption drops by
a factor of two. If I make the GUI larger/smaller the bandwidth
consumption increases/decreases.
Therefore, my working hypothesis is that the "system load" tab is
generating excessive X activity which translates to lots of bandwidth
consumption for the X-terminal case. I would not want to
significantly reduce the GUI size or time resolution to reduce that
bandwidth consumption so I may be stuck with this current consumption.
However, there was no such problem for the Debian wheezy case (where I
also routinely used an X-terminal) so I pretty sure there is some
other factor (e.g., exessive spatial resolution of these plots) that
could be adjusted so this GUI with "system load" tab displayed no
longer generates excessive X activity/bandwidth consumption.
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ksysguard depends on:
ii kde-runtime 4:4.14.2-2
ii ksysguardd 4:4.11.13-2
ii libc6 2.19-18+deb8u1
ii libkdecore5 4:4.14.2-5
ii libkdeui5 4:4.14.2-5
ii libkio5 4:4.14.2-5
ii libknewstuff3-4 4:4.14.2-5
ii libksgrd4 4:4.11.13-2
ii libksignalplotter4 4:4.11.13-2
ii libprocesscore4abi1 4:4.11.13-2
ii libprocessui4a 4:4.11.13-2
ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii libstdc++6 4.9.2-10
ksysguard recommends no packages.
ksysguard suggests no packages.
-- no debconf information
Reply to: