On Sun, May 24, 2015 at 7:26 PM, Loganaden Velvindron
<loganaden_at_gmail.com> wrote:
> On Sun, May 24, 2015 at 3:51 PM, Ish Sookun <ish_at_hacklog.in> wrote:
>> Hi Logan,
>>
>> On Sun, May 24, 2015 at 7:41 PM, Loganaden Velvindron <loganaden_at_gmail.com>
>> wrote:
>>>
>>> On Sun, May 24, 2015 at 3:31 PM, S Moonesamy <sm+mu_at_elandsys.com> wrote:
>>>
>>> We have a large latency and increasing bandwidth. At the Linux kernel
>>> level, you can see work sponsored by Google to make networking
>>> "faster". It's very important , as it gives the user a better
>>> experience.
>>
>>
>> Can you give a proper reference?
>>
>
>
> https://tools.ietf.org/html/rfc6928
>
Copy-paste from the RFC for a good explanation:
Today's Internet is dominated by web traffic running on top of short-
lived TCP connections [IOR2009]. The relatively small initial window
has become a limiting factor for the performance of many web
applications.
The global Internet has continued to grow, both in speed and
penetration. According to the latest report from Akamai [AKAM10],
the global broadband (> 2 Mbps) adoption has surpassed 50%,
propelling the average connection speed to reach 1.7 Mbps, while the
narrowband (< 256 Kbps) usage has dropped to 5%. In contrast, TCP's
initial window has remained 4 KB for a decade [RFC2414],
corresponding to a bandwidth utilization of less than 200 Kbps per
connection, assuming an RTT of 200 ms.
A large proportion of flows on the Internet are short web
transactions over TCP and complete before exiting TCP slow start.
Speeding up the TCP flow startup phase, including circumventing the
initial window limit, has been an area of active research (see
[Sch08] and Section 3.4 of [RFC6077]). Numerous proposals exist
[LAJW07] [RFC4782] [PRAKS02] [PK98]. Some require router support
[RFC4782] [PK98], hence are not practical for the public Internet.
Others suggested bold, but often radical ideas, likely requiring more
years of research before standardization and deployment.
Received on Sun May 24 2015 - 19:41:48 PST