On Mi, 23 dec 20, 11:48:31, David Wright wrote: > > Some sort of rough calculation between the expected/nominal bit rate > and the actual data rate achieved is certainly useful, if only to > ascertain whether the link itself is performing well. For that, you > need to reduce the amount of processing (like encryption) of the > data, and any other tasks tying up the CPU(s). Just for the test, > obviously. > > If you're still getting poor transfer rates, you might want to swap > cables and (if you're dealing with several hardware systems) cards. > For example, on the cable front, a cable with damaged blue or brown > pairs will give perfect 100BASE-T performance but not 1000BASE-T, > which uses all eight wires. (For the same reason, structural wiring > using brown for the telephone sockets will have the same problem.) Let's not forget the source and destination storage (connection). Even if the Gigabit (per second) interface on the PINE A64+ performs pretty well, a transfer larger that can fit in any buffers that might be involved will quickly be slowed down to the speed of the SD card and/or interface, respectively the USB2 connection for the hard disk (the board doesn't have SATA). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature