1 / 13

Throughput metrics and packet delay in TCP/IP networks

Samara State Aerospace University (SSAU), Russian Institute for Public Networks (RIPN). Throughput metrics and packet delay in TCP/IP networks. Andrei M. Sukhov, Samara State Aerospace University, amskh@yandex.ru Timur Sultanov, Samara State Aerospace University, tursul@rambler.ru

brooklyn
Télécharger la présentation

Throughput metrics and packet delay in TCP/IP networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Throughput metrics and packet delay in TCP/IP networks • Andrei M. Sukhov, • Samara State Aerospace University, amskh@yandex.ru • Timur Sultanov, • Samara State Aerospace University, tursul@rambler.ru • Mikhail V. Strizhov, • Samara State Aerospace University, strizhov@ip4tv.ru • Alexey P. Platonov, • Russian Institute for Public Networks, plat@ripn.net • Danil Polukarov, • Povolzhskiy State University of Telecommunications and Informatics, plkw@mail.ru Povolzhskiy State University of Telecommunications and Informatics (PSUTI)

  2. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Introduction One year ago, at RIPE 56 meeting in Berlin, we presented a method of measurement of available bandwidth between two points in a global network. Our method is based on measurement of network delay Di for packets of different sizes Wi. But before I would like to tell about two metrics. Two bandwidth metrics that commonly associate with a path are the capacity C and the available bandwidth Bav. The capacity C is the maximum IP-layer throughput that the path can provide to flow, when there is no competing traffic load (cross traffic). The available bandwidth Bav, on the other hand, is the maximum IP-layer throughput that the path can provide to flow, given the path's current cross traffic load. Bav C W1 W2 D1 D2 Figure 1: Two bandwidth metrics

  3. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) The Model (1) (2) (3) (4) (5) Figure 2: Packet Size vs Delay (6)

  4. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Utility AvBand We have developed utility AvBand (Available Bandwidth) that realize new method, using algorithm ping.Its advantage consist in possibility of working with any router, which responds to packages of inquiries ICMP Echo. Available Bandwidth

  5. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Changing packet size The design of the RIPE TTM system meets all requirements shown by our method, namely it allows to change the size of a testing package and to find network delay with a split-hair accuracy. By default, testing is conducted by packages in the size of 100 byte, but there is a page http://tt143.ripe.net:10259/cgi-in/configuration_targets.cgi corresponding to point of the menu «Configuration» of local Test Box. On which it is possible to add testing packages to RIPE Box up to 1500 byte in size with demanded frequency. In our case it is reasonable to add testing 1024 byte packages with frequency of 60 times in a minute. It is necessary to notice that the results of tests will be available on next day.

  6. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) new packet size testing frequency

  7. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Testing results Testing results are available in telnet to RIPE Test Box on port 9142. It is important to get the data from both ends of the investigated channel simultaneously, in the case presented here it is tt01.ripe.net and tt143.ripe.net. $ telnet tt143.ripe.net 9142 $ telnet tt01.ripe.net 9142 Obtained data will contain required delay of packages of the different sizes. Also, we need to distinguish packages.

  8. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) The data from sending Box Therefore at first it is reversible to sending Box and we will find lines: packet size Last value in string is sequence number of the packet. It is necessary to us to find this number on the receiving side at the channel.

  9. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) The data from receiving Box sequence number of the packet For set number of a package it is easy to find network delay, in our case - 0.044084 seconds. The following number of package 1039148557 has the size of 100 bytes and the delay is 0.043591 seconds. Thus, the difference - 0.000493 seconds

  10. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Average and minimum values tt143 -> tt01

  11. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) tt01 -> tt143

  12. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Calculation of bandwidth and capacity Then the required bandwidth and capacity of the link (tt143 -> tt01) can be calculated as The bandwidth and capacity of the return link (tt01 -> tt143) can be calculated as

  13. Samara State Aerospace University (SSAU),Russian Institute for Public Networks (RIPN) Additional measurements The main problem of our work is the little number of measurements. At this moment we made one experiment with RIPE TTM system that gives high precision of measurement and some local experiments. It is ideal to compare the results received by our method with values measured by alternative methods, first of all by means of the utility pathrate. Unfortunately, such tests are not made yet, we allocate only the speed of FTP downloading. It makes 3.04 – 3.20 Mbps in a direction from tt143.ripe.net to tt01.ripe.net and 3.2-3.3 Mbps in the opposite direction. We are looking for partners that can help us to make additional measurements with RIPE TTM system and utility pathrate.

More Related