(→Chromium Settings) |
|||
| Riga 16: | Riga 16: | ||
The bottleneck link queue can be governed by Drop Tail queue, AQM algorithms or flow queuing schedulers.These scripts employ iproute2 package and the NetEm Linux module. With tc “traffic control” is possible to set the queuing discipline, limit the link capacity and much more. The NetEm linux module can be employed to set the propagation delay. | The bottleneck link queue can be governed by Drop Tail queue, AQM algorithms or flow queuing schedulers.These scripts employ iproute2 package and the NetEm Linux module. With tc “traffic control” is possible to set the queuing discipline, limit the link capacity and much more. The NetEm linux module can be employed to set the propagation delay. | ||
| + | |||
| + | == Google Congestion Control Settings == | ||
| + | |||
| + | The Google Congestion Control algorithm is implemented in Google Chrome browser which is daily updated. To carry out the experimental investigation with the version of GCC according to the results that the reader wants to reproduce we recommend to downlowd and compile the: | ||
| + | * [https://www.chromium.org/developers/how-tos/get-the-code Download and Compile Chromium] | ||
== Web Server Settings == | == Web Server Settings == | ||
| − | |||
| − | |||
== Video Settings == | == Video Settings == | ||
== TCP Settings == | == TCP Settings == | ||
This web page provides the guideline and some scripts required to reproduce the experiments to evaluate the Google Congestion Control (GCC) for WebRTC. It can be used to reproduce the results obtained in the papers published in the context of the Google Faculty Research Award 2014 reported here.
Figure 1 shows an example of the experimental testbed topology. Two nodes, connected through an Ethernet cable, are used to run instances of the Chromium browsers, where GCC is installed, to generate WebRTC traffic and IPerf-like applications to generate concurrent TCP traffic. The experiments are orchestrated by the Controller that sends ssh commands to automatically start the WebRTC calls, start the TCP traffic and set the bottleneck parameters.
This repository contains the scripts used to emulate a WAN bottleneck link which in Figure 1 is shown on Node 1:
The bottleneck link queue can be governed by Drop Tail queue, AQM algorithms or flow queuing schedulers.These scripts employ iproute2 package and the NetEm Linux module. With tc “traffic control” is possible to set the queuing discipline, limit the link capacity and much more. The NetEm linux module can be employed to set the propagation delay.
The Google Congestion Control algorithm is implemented in Google Chrome browser which is daily updated. To carry out the experimental investigation with the version of GCC according to the results that the reader wants to reproduce we recommend to downlowd and compile the:
This web page provides the guideline and some scripts required to reproduce the experiments to evaluate the Google Congestion Control (GCC) for WebRTC. It can be used to reproduce the results obtained in the papers published in the context of the Google Faculty Research Award 2014 reported here.
Figure 1 shows an example of the experimental testbed topology. Two nodes, connected through an Ethernet cable, are used to run instances of the Chromium browsers, where GCC is installed, to generate WebRTC traffic and IPerf-like applications to generate concurrent TCP traffic. The experiments are orchestrated by the Controller that sends ssh commands to automatically start the WebRTC calls, start the TCP traffic and set the bottleneck parameters.
This repository contains the scripts used to emulate a WAN bottleneck link which in Figure 1 is shown on Node 1:
The bottleneck link queue can be governed by Drop Tail queue, AQM algorithms or flow queuing schedulers.These scripts employ iproute2 package and the NetEm Linux module. With tc “traffic control” is possible to set the queuing discipline, limit the link capacity and much more. The NetEm linux module can be employed to set the propagation delay.
We point out that the Google Congestion Control is implemented in Google Chome browser which is daily updated. In order to reproduce the results