Abstract
In this paper, we investigate three potential issues of the benchmarking measurement procedures defined in RFC 2544 and also used in RFC 5180 and RFC 8219. One of them is the lack of proper timeout usage. We use a Linux box, which can selectively delay a specified ratio of the packets. Using carefully selected parameters based on our preliminary measurements, we demonstrate that the experienced speed of the HTTP download is much less, than what could have been expected on the basis of the throughput results of the RFC 2544 tests. The other critical issue is the strict, absolutely zero loss criterion. We use a Linux box, which drops a specified small ratio of the packets. Whereas the RFC 2544 throughput results tend to be zero, the experienced speed of the HTTP download is quite good. The third problem is the lack of requirement for statistically relevant number of tests in the RFC 2544 benchmarking procedures. We demonstrate its severity with the latency benchmarking procedure defined in RFC 2544 and kept unchanged in RFC 5180 but redefined in RFC 8219.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Advances in Telecommunications, Electrotechnics, Signals and Systems
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
