From: Srikanth Sundaresan <srikanth@gatech.edu>
To: Nick Feamster <feamster@cc.gatech.edu>
Cc: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] about ready to do another build
Date: Sat, 21 May 2011 10:12:45 +0200 [thread overview]
Message-ID: <72E30C46-3045-4FBA-A464-C7120C3FECE2@gatech.edu> (raw)
In-Reply-To: <5C1FCBFC-B007-4B01-A7BA-6CCD5523DC34@cc.gatech.edu>
My concern about QoS is that without knowing the exact connection, it's pretty useless. If the QoS settings are less ( I think it's set to 128K up, I see 500k up in my hotel), then it's overly restrictive. If it's set to more than that, then it's useless as it never is activated. With long last mile DSL lines, which I think is the default here, it's impossible to predict the actual connection parameters, even if we knew the exact SLA.
It's easy enough to disable QoS during testing. More important than our testing is to make sure we don't cripple the internet connection. Unless the QoS setting is adaptive, I am opposed to turning it on unless we test it in a more controlled setting first.
- Srikanth
On May 21, 2011, at 12:12 AM, Nick Feamster wrote:
> Srikanth, Walter --- please chime in.
>
> Dave has a point here about the possibility of stopping QoS during testing.
>
> Thoughts?
>
> -Nick
>
>
> On May 21, 2011, at 12:11 AM, Dave Taht wrote:
>
>> And your customer experience will be poor, and you will be measuring tcp/ip malfunctioning rather than working properly.
>>
>> How hard would it be for your scripts, when doing bandwidth testing, to do a
>>
>> /etc/init.d/qos stop
>> do the test
>> /etc/init.d/qos start
>>
>> When do they do bandwidth testing? What script does it?
>
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
next prev parent reply other threads:[~2011-05-21 8:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 20:27 Dave Taht
2011-05-20 21:40 ` Nick Feamster
2011-05-20 21:41 ` Nick Feamster
2011-05-20 22:11 ` Dave Taht
2011-05-20 22:12 ` Nick Feamster
2011-05-20 22:15 ` Dave Taht
2011-05-20 22:16 ` Nick Feamster
2011-05-20 22:28 ` Dave Taht
2011-05-20 22:35 ` Nick Feamster
2011-05-20 22:42 ` Dave Taht
2011-05-20 22:47 ` Dave Taht
2011-05-20 23:22 ` Nick Feamster
2011-05-20 23:27 ` Dave Taht
2011-05-20 23:29 ` Nick Feamster
2011-05-20 23:27 ` Nick Feamster
2011-05-21 8:12 ` Srikanth Sundaresan [this message]
2011-05-21 12:09 ` Nick Feamster
[not found] ` <BANLkTikzEnRk8D0D4yR-4smqPiMYW0OH4A@mail.gmail.com>
2011-05-21 15:48 ` Srikanth Sundaresan
2011-05-21 16:08 ` Dave Taht
2011-05-21 16:33 ` Srikanth Sundaresan
2011-05-21 16:49 ` Dave Taht
2011-05-21 16:53 ` Nick Feamster
2011-05-21 17:07 ` Srikanth Sundaresan
2011-05-23 13:20 ` Jim Gettys
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=72E30C46-3045-4FBA-A464-C7120C3FECE2@gatech.edu \
--to=srikanth@gatech.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=feamster@cc.gatech.edu \
/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