From: Alan Goodman <notifications@yescomputersolutions.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Andy Furniss <adf.lists@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"lartc@vger.kernel.org" <lartc@vger.kernel.org>
Subject: Re: [Cerowrt-devel] Correctly calculating overheads on unknown connections
Date: Tue, 23 Sep 2014 00:02:57 +0100 [thread overview]
Message-ID: <5420AAA1.70203@yescomputersolutions.com> (raw)
In-Reply-To: <3136C05A-8069-4F04-B352-69A2BF3578FC@gmx.de>
On 22/09/14 20:52, Sebastian Moeller wrote:
>> >This test was ran on a BT Infinity VDSL/FTTC connection with the modem plugged directly into a CentOS 6 machine which is doing PPPoE. The connection is synced at 80mbit down and 20mbit up. BT restrict downstream speed to 77.44Mbps IP traffic.
> Thank you very much this is the first data set on a VDSL line I have seen, and clearly me hypothesis that overhead detection on PTM carriers will not work with the current code is nicely demonstrated. I need to ponder this a bit more and I might not be able to find a nice solution for those links...
You're welcome. If you need any more data feel free to drop me a line.
>>>I can run the test on a slower BT connection over the week end if anyone is interested in the results?
> I would love to see that especially if the other connection is much slower, as I see two possible issues with this data set:
The other connection is actually ADSL2, we probably know what the
results there will be... I think I shall run the test on a really slow
ADSL connection later in the year to double check my overheads though.
It seems like a very useful tool.
Also thanks for providing some example plots of how it should look.
That will allow me to better interpret results in future.
> 1) Speed: It might be that your line is fast enough to hide the ATM quantization below another quantization (like the 4KHz symbol rate of the individual carriers) or two many concurrent carriers;)
Would it be useful if I limited my upload speed with say hfsc to 1mbit
and re-ran the test?
Given the above comments in Sebastian’s very useful emails how would it
be best to shape these FTTC connections at present? Without overhead
set or something else?
Alan
next prev parent reply other threads:[~2014-09-22 23:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541C9527.1070105@yescomputersolutions.com>
[not found] ` <541DA8B5.70701@gmail.com>
2014-09-20 17:55 ` Dave Taht
2014-09-20 22:29 ` Andy Furniss
2014-09-21 18:35 ` Sebastian Moeller
[not found] ` <CAK1m8mPBWyg-sR-ekZGUhsOG-0HoZd3eJ-Q6HJpSLyN-J90kHg@mail.gmail.com>
2014-09-21 21:40 ` Alan Goodman
2014-09-22 9:05 ` Sebastian Moeller
2014-09-22 10:01 ` Andy Furniss
2014-09-22 10:20 ` Sebastian Moeller
2014-09-22 13:09 ` Alan Goodman
2014-09-22 19:52 ` Sebastian Moeller
2014-09-22 23:02 ` Alan Goodman [this message]
2014-09-23 9:32 ` Sebastian Moeller
2014-09-23 15:10 ` Andy Furniss
2014-09-23 17:47 ` Sebastian Moeller
2014-09-23 19:05 ` Andy Furniss
2014-09-23 22:16 ` Sebastian Moeller
2014-09-24 9:17 ` Andy Furniss
2014-09-24 16:23 ` Sebastian Moeller
2014-09-24 22:48 ` Andy Furniss
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5420AAA1.70203@yescomputersolutions.com \
--to=notifications@yescomputersolutions.com \
--cc=adf.lists@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=lartc@vger.kernel.org \
--cc=moeller0@gmx.de \
/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