From: Burak Gorkemli <burakgmail-jvt@yahoo.com>
To: dccp@vger.kernel.org
Subject: Re: [Announce]: Test results with latest CCID3 patch set
Date: Wed, 12 Dec 2007 20:40:57 +0000 [thread overview]
Message-ID: <402454.43276.qm@web30005.mail.mud.yahoo.com> (raw)
In-Reply-To: <20071210154008.GA16839@gerrit.erg.abdn.ac.uk>
>
> | The scenario that I mostly use is limiting the bandwidth with a
>
middlebox running TBF. However, all of the recent trees
> | except 2.6.20final_dccp (2.6.20 patched with Ian's
> modifications)
>
that I have tested fail to achieve acceptable transfer rates.
> Thank you for the report, but the material as-is does not help us
> very much. What is missing is the link speed of the
> ethernet cards that lead to the middlebox, and have you monitored
> the
loss rate p?
> Using a TBF in this setting means slowing down the link speed by
> a
factor of 10 .. 20, and unless you are using large
> FIFOs in addition to the TBF, the loss rate will very soon reach
> high
values.
>
Link speed is 100 Mbps, and I tested DCCP under various bottleneck
bandwidths, like 1000, 2000, 5000 and 10000 Mbps. I will repeat the
tests with dccp_probe enabled, and show the results in a website,
as soon as I have time.
> Therefore, can you please clarify what you mean by "acceptable
> transfer
rates": maybe the scenario is not supposed to
> warrant any high transfer rates at all. Which would mean
> expecting
something where not much can be expected - as said,
> without more detailed knowledge about how p reacts, these figures
> don't
tell us very much.
>
By acceptable transfer rates I was referring to the rates achieved
by 2.6.20final_dccp. But you are right, we cannot be sure of
the goodness of the results by comparing two DCCP stacks,
so I am giving TCP-Reno streaming results below under same
conditions, which should be a solid benchmark:
Bottleneck\x1000Kbps: 0.0-60.6 sec 6.91 MBytes 958
Kbits/sec
Bottleneck 00Kbps: 0.0-60.1 sec 13.7 MBytes 1.91 Mbits/sec
BottleneckP00Kbps: 0.0-60.1 sec 33.6 MBytes 4.69 Mbits/sec
Bottleneck\x10000Kbps,limitP000bytes: 0.0-60.1 sec 65.4 MBytes 9.13 Mbits/sec
The average transfer rates in the rightmost column show that
the configured bottleneck rates are achievable, hence I think
the transfer rates that 2.6.20final_dccp reaches seem acceptable,
whereas the rates of other trees are not.
> Didn't you have a web page with further information?
I will have soon, hopefully.
>
> Yes, please: the cleanest comparison would be to take a 2.6.24
> tree,
and compare the patch sets on the same basis. I almost expected that the
> results are not as good as the 2.6.20final_dccp -- it is an almost
> sure
indication that the difference is not due to the patches, and that
> there are other factors at work. By carefully looking at
> these
differences, we will be able to see clearer what is happening in the above.
>
I agree with you. 2 or 3 weeks ago I applied Ian's patches to
more recent trees (2.6.22 and 2.6.24) and the results were
not as good as 2.6.20.
> Again thanks a lot for posting results, hope you will be back with
> further information soon,
>
> Gerrit
>
I am planning to repeat the tests focusing on 2.6.24 and
post the results - with dccp_probe figures in my website.
Burak
next prev parent reply other threads:[~2007-12-12 20:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 15:40 [Announce]: Test results with latest CCID3 patch set Gerrit Renker
2007-12-11 13:59 ` Alessio Botta
2007-12-11 14:21 ` Gerrit Renker
2007-12-11 17:40 ` Arnaldo Carvalho de Melo
2007-12-12 14:45 ` Burak Gorkemli
2007-12-12 16:42 ` Gerrit Renker
2007-12-12 20:40 ` Burak Gorkemli [this message]
2007-12-12 23:19 ` Alessio Botta
2007-12-12 23:21 ` Alessio Botta
2007-12-13 0:29 ` Arnaldo Carvalho de Melo
2007-12-13 9:37 ` Gerrit Renker
2007-12-13 13:28 ` Burak Gorkemli
2007-12-13 14:14 ` Gerrit Renker
2007-12-13 16:35 ` 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=402454.43276.qm@web30005.mail.mud.yahoo.com \
--to=burakgmail-jvt@yahoo.com \
--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.