This is a great, but quite difficult, goal. Coming from a performance testing background, I’d have to say that measurements aren’t usually useful unless repeatable.
If your goal is to determine whether you should use a wireless network or wired for better performance, then you probably want to do something like a large file transfer between your endpoint and another in your local network, timing the transfer. Both endpoints should be nearly idle, so that other activities aren’t impacting the transfer. Here are some things that might vary timing: other endpoints on the same network that are generating or receiving traffic; file data block buffering at each end (the first time you send a file, it will be read from disk, but if you send it again immediately, part of the file may be cached); neighboring wireless networks may create interference when they are very active. And the target endpoint may not really be the best to emulate your real endpoints for your normal activities.
But for just the question of wired versus wireless, that should give you a fair idea. And usually your wireless router will have some statistics that can show interference, such as when your neighbors are streaming over their wireless network.
Thanks for your reply.
My question is more about measuring consistency than peak performance.
I do not really care if I get 50 MB/s peak, for sure I can saturate it, I see it during download.
For example, if I could measure a sort of “response time”: how does it take for each packet transferred from/to device to/from router, plot the values over time (maybe a day); change to Ethernet the next day, overlay the plots.
If, from this measurement, I see that the “response time” with Ethernet is ~10 ms, and 10-50 ms for Wifi, this would be great.
Apart doing some statistics: average, standard deviation, …
The measurement has to be done during normal use; ping, iperf3 will give me momentary situation.
Well, the “response time” concept doesn’t work well here. The router doesn’t “respond” to each packet, it forwards it to the destination address. You can measure the total amount of traffic sent or received per unit time, which is that “bandwidth” concept; you can measure the amount of time it takes to complete a “transaction” such as a file transfer or web page load. A “ping” test is another type of transaction which will give you an idea of how busy the network segments and store-and-forward devices such as switches and routers are along the path to your destination. For the latter, if you were to ping an endpoint outside your local network, you have to understand that the packets will take varying paths to the destination, and routes and endpoints may change from moment to moment due to load balancing.
Perhaps for what you are seeking you can ping your home router from your workstation a number of times per hour and record the ping response time and variance, comparing the measurements for wired and wireless.