I'm counting a total of 21 peers.  And it should still report actual
bandwidth used with many peers.

I got bandwidth used like this (script I wrote):

wget www.chaosreigns.com/code/dl/netload.pl
chmod +x netload.pl
./netload.pl 60
 dev  rx mrx  tx mtx  dev  rx mrx  tx mtx  dev  rx mrx  tx mtx 
eth0 41.4/41.4 11.7/11.7 vboxnet0 0.0/0.0 0.0/0.0 wlan0 0.0/0.0 0.0/0.0 
eth0 42.8/42.8 12.2/12.2 vboxnet0 0.0/0.0 0.0/0.0 wlan0 0.0/0.0 0.0/0.0 
eth0 42.8/42.8 13.3/13.3 vboxnet0 0.0/0.0 0.0/0.0 wlan0 0.0/0.0 0.0/0.0 

So that's:  (network device) (receive speed)/(max receive speed)
(transmit speed)/(max transmit speed) (network device)...

The relevant numbers are the second column: 41.4, 42.8, 42.8 - kilobytes
per second.  With azureus throttled at 37 kilobytes per second.

The argument to netload is the number of seconds per reporting period,
so one minute.

That script is pretty simple, and at least 9 years old.  It reads
/proc/net/dev, which includes, for each device, bytes received and bytes
transmitted since the last boot.  The values wrap, I don't remember
where.

If you find some other way of reporting average bandwidth for more than
a fraction of a second, like this, let me know.  The gnome panel System
Monitor seems unsuitable due to very small sample periods.

I shut all my other network applications down for the test.  Browsers
can use a scary amount of bandwidth while doing nothing.

Thanks for taking the time to attempt to confirm.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428231

Title:
  Badly under-reports bandwidth usage.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to