From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: CCID 3 performance - some further thoughts
Date: Tue, 05 Dec 2006 20:19:32 +0000 [thread overview]
Message-ID: <200612052019.32837@strip-the-willow> (raw)
I have been experimenting with CCID 3 on various computers,
below is a list of observations:
* I didn't use netem or anything (no loss), yet the receiver reported loss
* I quite frequently got those messages from tfrc_calc_x, like
tfrc_calc_x: Value of p (29) below resolution. Substituting 100
This should not happen - I believe that these p measurements are bogus
and we should check if the loss rate computation is ok.
* the behaviour of iperf is very unpredictable, sometimes it seems that
throughput is directly related to current system load
* the RTT values are almost always higher than the RTT computed by ICMP
ping - highly desirable to find ways of obtaining sharper estimates
* would it make sense to define an RTT cut-off value, such as e.g. 2MSL
(120 seconds) and regard all RTT estimates above this value as nonsensical?
E.g.: #define DCCP_SENSIBLE_RTT_VALUE_MAX 120 * USEC_PER_SEC
- Gerrit
next reply other threads:[~2006-12-05 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 20:19 Gerrit Renker [this message]
2006-12-05 20:39 ` CCID 3 performance - some further thoughts Ian McDonald
2006-12-05 21:26 ` Gerrit Renker
2006-12-05 21:38 ` Ian McDonald
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=200612052019.32837@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.