On Thu, 13 May 2021, Russell Senior wrote:
You do want to be looking at the whole picture though, not just
firefox. Those numbers are way too low to be your online meeting.
You might want to track total in/out bytes of the interface. Before
and after your meeting run ifconfig -a. For each interface, you should
see a line like:
RX bytes:7251003175 (7.2 GB) TX bytes:282820023 (282.8 MB)
Or, if you like iproute2 tools instead, ip -s link, where you will see
lines like this:
RX: bytes packets errors dropped overrun mcast
7255250852 7218804 0 0 0 0
TX: bytes packets errors dropped carrier collsns
284958814 1699378 0 0 0 0
Subtracting the before numbers from the after numbers, you should get
the aggregate "during" numbers.
I know that Russell is aware of this, but it's worth noting that
aggregate numbers won't necessarily be limited to your Zoom session.
Your package manager may be configured to look for updates every once
in a while; a cron job may kick off a network session; any local
network filesystem activity can bump the aggregate.
Perhaps none of those scenarios applies to your system during the Zoom
call, but beware that they will impact your numbers.
--
Paul Heinlein
heinl...@madboa.com
45.38° N, 122.59° W
_______________________________________________
PLUG: https://pdxlinux.org
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
