Joint experimentation of modern Internet application Dr. Ioannis Giannoulakis Eight Bells Ltd giannoul@8bellsresearch.com protocols with SDN www.8bellsresearch.com (Go-Quick) Fed4FIRE+ Open Calls March 15th, Paris, France WWW.FED4FIRE.EU
Project Summary Ø Go-Quick experimentation aims to evaluate the performance of QUIC, as compared to HTTP and SPDY/HTTP2, through deploying virtual overlay networks on Fed4FIRE+ OpenFlow SDN-enabled infrastructure. Ø Since sophisticated congestion avoidance and packet error correction mechanisms are used in all protocols, the actual network scenarios of the Go-Quick experiments determine which protocol performs best in each case. Ø By deploying various network conditions and for different size of objects, performance metrics like throughput are assessed for the three protocols, QUIC, SPDY/HTTP2, and HTTP. Ø Different virtual overlay networks are deployed on Fed4FIRE+ OpenFlow SDN-enabled infrastructure to adapt to changing network scenarios. 2 WWW.FED4FIRE.EU
Objectives Ø Deployment of a virtual overlay network on Fed4FIRE+ OpenFlow SDN- enabled infrastructure Ø Installation and configuration of QUIC, APACHE servers and emulation of different network conditions Ø Google’s QUIC Client and Server are meant mainly for integration testing: neither is performant at scale Ø Go Quick has developed Bash scripts for full automation of the experiments Ø Performance evaluation of QUIC as compared to other L7 protocols (e.g., HTTP/HTTP2) 3 WWW.FED4FIRE.EU
Go Quick Topology OFELIA VTAM & OFAM aggregate managers HTTP HTTP Server Client HTTP2 HTTP2 Server Client OFELIA Switches QUIC QUIC File A Server Client OFELIA server host OFELIA client host 4 WWW.FED4FIRE.EU
Internet Protocols in a nutshell Ø One of the bottlenecks of HTTP performance is the opening of too many TCP connections to achieve concurrency. A large portion of HTTP data flows consist of small (less than 15KB), bursty data transfers over dozens of distinct TCP connections. Ø Another limitation is that HTTP based web transfers are strictly initiated by the client. This presents a serious problem because it hurts performance significantly in the case of loading embedded objects. Ø HTTP2 introduces request prioritization. The client is allowed to specify a priority level for each object and the server then schedules the transfer of the objects accordingly. Ø QUIC is working over UDP. The protocol does not force *P. Megyesi, Z. Kramer, S. Molnar, “How quick is QUIC?”, in in-order delivery of packets thus QUIC avoids HOL Proc. of IEEE ICC 2016, 22-27 May 2016. blocking. 5 WWW.FED4FIRE.EU
Results QUIC – SERVER & CLIENT Ø QUIC aims to improve performance QUIC - quic_client 90 compared to HTTP, HTTP2 by 80 QUIC quic_client 70 multiplexing web objects in one 10MB 60 QUIC quic_client stream over UDP 50 Mbps 1MB 40 QUIC quic_client 100KB 30 Ø “Go Quick” performed a comparative QUIC quic_client 20 10KB analysis 10 0 1 2 4 8 10 15 20 30 40 50 60 80 100 200 500 1000 Files 6 WWW.FED4FIRE.EU
Results QUIC SERVER – CHROME CLIENT QUIC - Chrome Ø Performance is greatly affected by 80 70 the file size and the number of 60 QUIC chrome concurrent file requests. 50 10MB Mbps 40 QUIC chrome Ø OFELIA SDN physical switches 30 1MB 20 QUIC chrome were configured to route data 100KB 10 and to create congestion and QUIC chrome 0 10KB losses according to the network 1 2 4 8 10 15 20 30 40 50 60 80 100 200 500 1000 scenarios of the experiment. Files 7 WWW.FED4FIRE.EU
Results QUIC HTTPS HTTPS2 (100KB) QUIC - https - https/2 100KB Ø In all scenarios QUIC protocol is 250 QUIC quic_client outperformed by HTTPS/HTTPS2 200 Ø For typical web object sizes and for QUIC chrome 150 a big number of objects (i.e., many HTTPS wget Mbps parallel flows), HTTPS2 is up to 80% 100 HTTPS chrome (apache 2.4.18 mpm prefork) better. 50 HTTPS chrome (apache Ø In future work, measurements with 2.4.27 mpm event) 0 HTTPS/2 chrome (apache Google Sites Server will be 2.4.27 mpm event) 1 2 4 8 10 15 20 30 40 50 60 80 100 200 500 1000 collected to exploit multi-threading Files capabilities 8 WWW.FED4FIRE.EU
Network conditions under congestion 4 SCENARIOS USING SDN AND LINUX TC TOOL Negligible delays and losses. Ø Ø only delay by the interfaces and routing software Comparatively low values for delays and losses. Ø Ø delay of 12.5 ms is added and losses of about 0.5%, both upstream and downstream Moderate values for delays and losses. Ø Ø delay of 25 ms is added and losses of about 1%, both upstream and downstream Moderate values for delays and losses. Ø Ø delay of 50 ms is added and losses of about 2%, both upstream and downstream Comparatively high values for delays and losses. Ø Ø delay of 100 ms is added and losses of about 4%, on both upstream and downstream 9 WWW.FED4FIRE.EU
Throughput rate under the 4 scenarios 1000 Ø QUIC is affected less by losses and network delays 100 https_1MB http2_1MB quic_1MB https_100KB 10 http2_100KB quic_100KB https_10KB 1 http2_10KB quic_10KB 0.1 0_0.0 12.5_0.5 25_1.0 50_2.0 100_4.0 10 WWW.FED4FIRE.EU
Benefits gained for Eight Bells Ø Go-Quick project leveraged the OpenFlow OFELIA testbed provided by Fed4FIRE+ (i2CAT) for the small-scale experiment on real equipment. Ø Eight Bells plans to invest in studying network services and their interactions, therefore it had access to cutting edge technology environments for transport layer applications. Ø Our analysts found into the Fed4FIRE+ experimentation testbed an SDN-capable platform with diverse set of capabilities and experimentation tools. 11 WWW.FED4FIRE.EU
Business Impact Ø 8BELLS is a start-up company specializing in modelling and analysis for businesses as well as in selected parts of Information ICT, based in Nicosia, Cyprus. Ø The company has been established recently by ICT researchers and financial analysts pursuing the application of their research expertise and innovations in the ICT related arena. Ø 8BELLS delivers customizable solutions that enhance modern communications relevant to the area of 5G Mobile Technology, NFV and also management solutions for Cloud infrastructures. Ø 8BELLS translates business data into financial models, providing forecasts and supporting decision makers. 12 WWW.FED4FIRE.EU
Business Impact Ø Eight Bells plans to provide evaluation reports and research studies based on the outcomes of Go-Quick. Ø The company cooperates with network operators and other ICT stakeholders that will be interested on the experimental results. Ø The innovative approach of Go-Quick experiment will consist a basis for a technical modelling framework in the existing company’s portfolio. 13 WWW.FED4FIRE.EU
Feedback to Fed4FIRE Ø OFELIA testbed proved powerful enough to support the required VMs. Ø Also flexible enough to adapt to the diverse topology demands, during the experiment. Ø The support of the Patron (i2CAT) was valuable for the smooth execution of the experiment. Ø Fruitful discussions and exchange of ideas took place during past meetings of Fed4FIRE. 14 WWW.FED4FIRE.EU
www.8bellsresearch.com WWW.FED4FIRE.EU This project has received funding from the European Union’s Horizon 2020 research and innovation programme, which is co-funded by the European Commission and the Swiss State Secretariat for Education, Research and Innovation, under grant agreement No 732638.
Recommend
More recommend
