MB or GB of DATA/sec. would be a useful measurement. A benchmark usually consists of uploading or downloading various file sizes (a few larger files will typically yield a higher throughput than a plethora of small files) and reading the results. You could read packets/sec, but since each packet could contain a different amount of data, that’s not a representative measurement.

What we really want to know is how fast we can move a file or files from point A to point B. Example: you may have a 1Gb/sec pipe, but if it only moves real world data at 60 MB/sec (the theoretical max is 125MB/sec) due to latency, errors and retries, that’s what really matters.

The two pipes have the same speed but the larger pipe produces more volume. In my example, the speed of the water in both pipes is the same. This represents internet speed. The larger the pipe the more volume/sec can be produced. This is the bandwidth and represents the amount of data that can be moved per unit of time. If large amounts of data, info are demanded the internet speed must provide the power to move the data packets. If the volume demand increases the internet speed may slow down. I hope this clears things up.

The two pipes have the same speed but the larger pipe produces more volume. In my example, the speed of the water in both pipes is the same. This represents internet speed. The larger the pipe the more volume/sec can be produced. This is the bandwidth and represents the amount of data that can be moved per unit of time. If large amounts of data, info are demanded the internet speed must provide the power to move the data packets. If the volume demand increases the internet speed may slow down. I hope this clears things up.