Bart Salaets – is Solutions Architect in F5 Networks specifically focusing on service providers in the EMEA region. Prior to this, he has held IP consulting and technical leadership positions in Juniper Networks, Redback Networks and Alcatel-Lucent, giving him more than 15 years of experience in both fixed and mobile broadband IP network design. Bart Salaets was born and still lives in Belgium and holds a Masters degree in Electrical Engineering from the Catholic University of Leuven, Belgium and an MBA from Flanders Business School in Antwerp, Belgium.
Topic of Presentation: Optimising TCP in today’s changing network environment
Language: English
Abstract: The need to juggle performance across wired, wireless and wi-fi networks is a challenge as each of these paths has very different characteristics when it comes to TCP. Tuning the TCP stack to be optimized for the varying degrees of packet loss, latency and congestion on the different connection types is a challenge. This session will cover tuning several aspects of your network and the underlying TCP stack to deliver an optimized application experience for all users. Topics will include:
Choosing the correct Congestion Control algorithm
Optimizing TCP with techniques like TCP buffering and adjusting TCP window sizes
Rate-based pacing to help multiple request/responses over a single connection
Google has tested implementing SPDY on a representative group of 25 of the top 100 internet sites, and observed speed improvements from 27% to 60%.
CMU study showed ~50% improvement of the Mean Doc Load Time, which is the time taken for the document object
model (DOM) to load completely. Based on measurement of 25 top visited websites.
Data and Network Optimization Effect on Web Performance
Steven Rosenberg, Surbhi Dangi, Isuru Warnakulasooriya
February 10, 2012
CMU-SV-12-001
To provide the best subscriber QoE, your ideal TCP stack would do a few things for you.
It would promote high goodput so that you are always maximizing the amount of data being pushed through your network that is relevant to your subscriber. The higher your goodput, the faster your subscribers get the information they want.
It would minimize buffer bloat so you can reduce congestion before it even starts. Buffer bloat is a sign of far too much traffic on a network that can’t handle it, leading to increased delays of your data being sent to your subscribers. Minimizing buffer bloat means less delay which means faster performance for your subscribers.
And finally, it would keep fairness between your flows so no one flow gets dropped. A dropped flow leads to the lowest form of subscriber QoE, thus keeping all flows alive is the best scenario.
These three characteristics: high goodput, minimal buffer bloat, and flow fairness, would all work together to optimize your network and your subscribers’ QoE.