[Bismark-devel] about ready to do another build

[Nick Feamster]

Perhaps we can disable it by default, but (1) suggest QoS settings based on our measurements (2) give people a link for where to set them.  We could perhaps even provide a button on the Web interface to automate an update of the QoS settings.

-Nick

On May 21, 2011, at 10:12 AM, Srikanth Sundaresan wrote:

> 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 at lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bismark-devel
>