[iccrg-slowstart 00006] Re: [Iccrg] SSDT contributions
michael.scharf at ikr.uni-stuttgart.de
Tue Apr 15 20:33:04 BST 2008
in simple usage scenarios (e. g., HTTP/1.0-like communication) the
impact of Slow-Start is rather obvious, as well as the potential
speedup that faster algorithms could achieve.
The attached slides show some Linux measurement results that compare
the Slow-Start with Quick-Start (best case). There can be a
performance improvement of one second or more, which is typically
"user perceivable". The difference would be even larger if the TCP
stacks used delayed ACKs (Linux disables them sometimes). Of course,
the larger the RTT, the more significant is the effect.
I also have data for more realistic HTTP request patterns, but in this
case the Slow-Start impact is more difficult to quantify and depends a
lot on the application communication pattern.
On Fri, 11 Apr 2008 at 10:45:20, Dirceu Cavendish wrote:
> I think the "user perceivable" impact of faster SS algorithms should be documented within ICCRG. Do you have data backing that up (for any application of your choice)?
> I am attaching few slides on experimental results in reducing segment losses during SS, for discussion. As presented in Manchester, we reduce losses by both reducing the speed of cwnd increase (in a fractional rather than by 1 way), as well as NOT transmitting the entire cwnd on a back-to-back fashion - introducing "micro-pauses" during transmissions...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 37740 bytes
Desc: not available
Url : http://oakham.cs.ucl.ac.uk/pipermail/iccrg/attachments/20080415/86b57083/ss_vs_qs-0001.pdf
More information about the Iccrg