Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SQM Question #3: How shall we recommend people set their upload/download speeds?
Date: Sun, 29 Dec 2013 00:53:49 -0800	[thread overview]
Message-ID: <CAA93jw43jm6SBwSswmG6Xvs02nvrs=q=5372H7RV7EN9QW0geg@mail.gmail.com> (raw)
In-Reply-To: <54B228A1-9362-4CC5-BDC6-C8968A5DDE94@gmail.com>

On Sat, Dec 28, 2013 at 8:33 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> QUESTION #3: How shall we recommend people set their upload/download speeds?
>
> Although we have already spent a lot of time on the list batting around ways to think about this, it seems to me that there are only two choices for recommendations, especially given that most people looking at CeroWrt are in a “TL;DR” mind set:

What does TL;DR mean?

> 1) If you don’t have an accurate sense of your actual link speed (e.g., you haven’t done a link speed measurement), you should take your provider’s published specs, knock them down by 15%, and enter those values in the SQM Basic Settings tab. [Or should they take an additional 15% off that already reduced value?]

92% on the up, 85% on the down are starting points.

>
> 2) If you have done measurements of your link speed, you should enter values that are 95% of each direction’s measured speed.
>
> Is this the right recommendation?

A short rant on the inadaquacy of speedtest and other tests would be
nice. Netanalyzr is the closest thing to a good test these days but it
requires java and is inaccurate above 20mbit.

>
> NB: In the Details… section, we can recommend ways to measure current link speeds, encourage people to make the measurement during quiet times, link to the “Quick test for Bufferbloat” page, etc. for those who want to dig further.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2013-12-29  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29  4:33 Rich Brown
2013-12-29  8:53 ` Dave Taht [this message]
2013-12-29 11:46   ` Sebastian Moeller
2013-12-29 13:52     ` Dave Taht

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='CAA93jw43jm6SBwSswmG6Xvs02nvrs=q=5372H7RV7EN9QW0geg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    /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