Control: notfound -1 4:5.8.5-1 ¡Hola Alan! El 2015-11-07 a las 16:17 -0800, Alan W. Irwin escribió:
Package: ksysguard Version: 4:4.11.13-2 Severity: normal
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.
Sorry for taking so long on getting back to you.I'm not sure if thinclients are a valid Plasma usecase, since even qt5 is requiring OpenGL now, so you will be forced to use a software OpenGL renderer.
But, this issue seems to be fixed. Using the plasma 5 version and doing: ssh -X localhost ksysguard "nethogs -a lo" shows me a peak consumption of 20 KB/s while running. Please let me know if this is fixed for you too. Happy hacking, -- "Programs must be written for people to read, and only incidentally for machines to execute." -- Hal Abelson, "Structure and Interpretation of Computer Programs" Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: PGP signature