From: Johannes Deleu <Johannes.Deleu@intec.ugent.be>
To: dccp@vger.kernel.org
Subject: mail voor linux mailinglist
Date: Thu, 22 Jun 2006 12:41:42 +0000 [thread overview]
Message-ID: <449A9006.9030608@intec.ugent.be> (raw)
Hi,
for a project, we're interested in using DCCP. As such, I did some
performance measurements with the latest version of the DCCP
implementation. To my opinion, they are not really what I expected.
Could you give some ideas or maybe some information about the current
status of the implementation (e.g. is packet loss detection planned for
implementation, when ?) ?
Results of similar tests are also interesting to see if they compare.
For the tests, I used an impairment node (based on linux, which
introduced some packet loss).
Measurements where performed with the patched iperf on linux-2.6.16.20
and I came to the following table:
TCP DCCP-CCID3 (Send/Recv)
No drop 94 Mbps 93.3 Mbps 93.2 Mbps
Drop 1% 83.4 Mbps 93.3 Mbps 92.3 Mbps
Drop 5% 16.6 Mbps 93.3 Mbps 88.6 Mbps
Drop 10% 3.25 Mbps 93.3 Mbps 83.9 Mbps
The transmitter does not detect the packet loss and doesnt slow down,
instead it keeps sending <CCID option 192 4294967295>.
As CCID3 is TFRC, I expected similar results for TCP and DCCP-CCID3.
When i tried out linux-2.6.17.1 (no packet drop) the receiver seems to
stop sending feedback packets after a while and the transmitter slows
down. The receiving process doesnt receive any data (recv doesnt return).
[ 3] local 10.0.1.3 port 3743 connected with 10.0.1.1 port 5001
[ 3] 0.0- 1.0 sec 11.0 MBytes 92.5 Mbits/sec
[ 3] 1.0- 2.0 sec 10.9 MBytes 91.6 Mbits/sec
[ 3] 2.0- 3.0 sec 10.9 MBytes 91.6 Mbits/sec
[ 3] 3.0- 4.0 sec 10.9 MBytes 91.6 Mbits/sec
[ 3] 4.0- 5.0 sec 10.9 MBytes 91.6 Mbits/sec
[ 3] 5.0- 6.0 sec 10.9 MBytes 91.6 Mbits/sec
[ 3] 6.0- 7.0 sec 6.86 MBytes 57.5 Mbits/sec
[ 3] 7.0- 8.0 sec 194 KBytes 1.59 Mbits/sec
[ 3] 8.0- 9.0 sec 100 KBytes 819 Kbits/sec
[ 3] 9.0-10.0 sec 100 KBytes 819 Kbits/sec
[ 3] 10.0-11.0 sec 100 KBytes 819 Kbits/sec
[ 3] 11.0-12.0 sec 100 KBytes 819 Kbits/sec
[ 3] 12.0-13.0 sec 100 KBytes 819 Kbits/sec
best regards,
Johannes
next reply other threads:[~2006-06-22 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 12:41 Johannes Deleu [this message]
2006-06-24 22:36 ` mail voor linux mailinglist 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=449A9006.9030608@intec.ugent.be \
--to=johannes.deleu@intec.ugent.be \
--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