From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Sensitivity of TFRC throughput equation wrt to changes of RTT
Date: Fri, 13 Apr 2007 12:03:02 +0000 [thread overview]
Message-ID: <200704131303.03072@strip-the-willow> (raw)
The comment by Dave brought me back to check what a change of
a factor of 10 does to the throughput in TFRC.
RFC 3448 gives in section 8 the following alternative format
of the throughput equation (which is directly responsible for
the alllowed sending rate X):
s
X = --------
R * f(p)
This shows that the dependence is reciprocal. Thus using an RTT
which differs by a factor of 10 to account for in-stack processing
results an a throughput reduction of factor 10.
In other words, 90 Mbits/sec becomes 9 Mbits/sec.
next reply other threads:[~2007-04-13 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 12:03 Gerrit Renker [this message]
2007-04-13 19:33 ` Sensitivity of TFRC throughput equation wrt to changes of RTT David Miller
2007-04-13 19:52 ` Ian McDonald
2007-04-13 20:27 ` Gerrit Renker
2007-04-13 20:43 ` David Miller
2007-04-13 20:54 ` David Miller
2007-04-14 5:43 ` Eddie Kohler
2007-04-15 16:15 ` Gerrit Renker
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704131303.03072@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.org \
/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