YENRA — NETWORK PATH AND MEASUREMENT WORKSHEET
Updated October 5, 2026
Guide: https://yenra.com/multi-gigabit-networks/

PURPOSE
Identify a limiting component before upgrading a network you administer.
Open in a text editor and duplicate each segment or measurement record.
Schedule load tests away from work requiring stable network performance.

WORKLOAD
Task to improve / acceptable completion time:
Local transfer or Internet transfer:
Source device and storage / destination device and storage:

PATH SEGMENT (repeat from source to destination)
Device/port A -> cable/channel -> device/port B:
Supported rates at both ends:
Negotiated rate / date checked:
Cable type / approximate length / patch-panel connections:
Adapter bus or uplink limits:
Model-specific documentation:
Interface errors or retransmissions observed:

RAW RATE CONVERSIONS (decimal; divide bits by 8)
1 Gb/s = 125 MB/s; 2.5 Gb/s = 312.5 MB/s;
5 Gb/s = 625 MB/s; 10 Gb/s = 1,250 MB/s.
Application throughput is lower after protocol overhead and other limits.
MB/s and binary MiB/s differ. Keep the source tool's units with every value.

MEASUREMENT
Date / time / software versions / other traffic:
Endpoint CPU/storage observations:
Network test forward / reverse / units:
Representative file size / copy time / throughput / cache conditions:
Single change made / repeated result:

OPTIONAL IPERF3 TEST ON YOUR ADMINISTERED PRIVATE LAN
Use capable wired endpoints. On the test server: iperf3 -s
On the client, substitute the actual server LAN address for SERVER_LAN_IP:
iperf3 -c SERVER_LAN_IP -t 20
iperf3 -c SERVER_LAN_IP -t 20 -R
Scope any temporary firewall allowance to the intended private test.
Stop the server and remove temporary allowances when done.
Official method: https://software.es.net/iperf/invoking.html

FICTIONAL EXAMPLE
Storage sustains 180 MB/s while the link is 2.5 Gb/s.
180 x 8 = 1,440 Mb/s = 1.44 Gb/s of file data.
Upgrading only the network to 10 Gb/s cannot remove this storage limit.
Repeat the test and account for caching before drawing that conclusion.

DECISION
Observed limiting component / evidence:
Proposed change / cost / compatibility checks:
Retest showing useful improvement: