GNOME Bugzilla – Bug 626738
Relative Network Bandwidth
Last modified: 2012-08-07 22:39:11 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/614848 "At the moment GNOME System Monitor always shows network traffic relative to maximum traffic achieved in particular time window. I'd like to be able to insert in System Monitor my max network speed and System Monitor to show my traffic according to it. E.g. I have 4Mbps (400KBps) link and I'd like to see how much (what bandwidth) of it I currently use. System Monitor does not show it at the moment. If I recently had 100KBps as maximal network speed, it uses this speed as upper limit and shows all other measurements relative to (below) it. Seems to me not very useful." Thanks,
I don't think it's possible to find the internet connection bandwidth, so showing the bandwidth relative to the maximum value measured so far seems the best solution. We could use the bandwidth of the network card and display values relative to that, but network cards are usually 100Mb/s or 1000Gb/s, and the internet speed is usually lower, and in case of 1000Gb/s cards, the internet usage would be almost 0% of the 1000Gb, so it would not be really useful neither. So maybe storing the maximum speed used so far would help a bit, and showing everything relative to that. So each time your network load is higher then a current maximum stored, the maximum would get saved, so after you have fully used your 4Mbps bandwidth for the first time you would get the correct behavior. A request to be able to set the range for the network charts is in bug 590107, and the automatic behavior is the one described above.
[Adding missing "QA Contact" entry so system monitor bug report changes can still be watched via the "Users to watch" list on https://bugzilla.gnome.org/userprefs.cgi?tab=email when the assignee is changed to an individual.]
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 590107 ***