From: <BeckW@telekom.de>
To: <bloat@lists.bufferbloat.net>
Subject: [Bloat] some market observations
Date: Fri, 11 Mar 2011 14:22:12 +0100 [thread overview]
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D016E72AA15@HE111648.emea1.cds.t-internal.com> (raw)
interesting discussions going on here..
A consumer-oriented magazine complained that a VDSL access rated 50 mbps only delivered 31 mbps. It turned out that they used a single TCP session for their measurements. At those speeds, delay and packet loss determine the maximum throughput, independent of the available bandwidth. The formula in RfC 3819, Section 8.5 yielded an estimate of ~32 mbps for the given delay and loss, which matched nicely the actual measurements.
With increasing access bandwidths, ISPs are forced to look into the delay issues.
DSL bit error rates go up when everybody switches to DSL. DSL standard bodies look into link layer mechanisms to mitigate this, but all solutions add delay. It's hard to find the right balance between delay and packet loss; both hurt TCP performance. As delay can't be controlled by a single ISP, the temptation is high to focus on the bit errors.
Regards,
Wolfgang Beck
next reply other threads:[~2011-03-11 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 13:22 BeckW [this message]
2011-03-11 19:05 ` Srikanth Sundaresan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=580BEA5E3B99744AB1F5BFF5E9A3C67D016E72AA15@HE111648.emea1.cds.t-internal.com \
--to=beckw@telekom.de \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox