In a recent study how network protocol stack performance test, think of online information is one-sided talking about how to carry out network performance testing, rather than the stack itself. After watching a lot of information, I think the test network protocol stack and only the following three indicators:
: 1. The transmission rate by the amount of information is called channel transmission bits per second transmission rate, which is received and the rate at which data is sent, the unit is bits per second (b/s), hereinafter referred to as bitrate, using wget/FTP download/upload speed testing, or write a simple server/client side, add test transmission rate in the network environment,
2. Throughput: throughput is to point to in the absence of frame loss, equipment can accept and forward maximum data rate, which is the real transmission limit, use iperf3 in testing at a certain rate to send a certain number of frames, frame, and calculate the equipment under test if send frame and receive equal number of frames, then will send rate and test again; If the received frame less than send frame to send speed testing, until the final results, throughput test results expressed in bits/SEC or bytes/SEC,
3. The processing time delay: add a timestamp, testing protocol stack terminal to read and send to drive time,
, in addition to other indicators, such as: bandwidth utilization rate are not indicators to the performance of the network protocol stack, such as:
Bandwidth, I think it is a hardware to provide a fixed value, and the performance of the network protocol stack is no relation, and utilization of bandwidth, I think that is the process of test throughput, the throughput is higher, it shows that the performance of the protocol stack, the better
Utilization: only operators' concerns, rather than the performance of the network protocol stack, for example, a highway designated can run 100 vehicles, then run 10 is only 10%, run 100 is 100%.
have a great god would add ah