Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dane Medic <dm70dm@gmail.com>
To: Dave Taht <dave.taht@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Torrents are too fast
Date: Thu, 20 Nov 2014 17:25:14 +0100	[thread overview]
Message-ID: <CABsdH_E=oGF4xZtwnsYFzLq5=JqWu9rHbby9JMzVG4mi-g6a9g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4owDhMB3r0HEyewRLeO3fNGJw=vSCr7OyBU0vO0k4_bQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4156 bytes --]

Thank you for advice Dave. I'm just looking around how to set-up layer 7
inspection, I've also found this ->
http://luci.subsignal.org/trac/browser/luci/trunk/contrib/package/freifunk-p2pblock?rev=
It would be very nice if someone could "merge" this with simple.qos, I
don't really know how, yet.

2014-11-20 15:40 GMT+01:00 Dave Taht <dave.taht@gmail.com>:

> I would be surprised if you could tolerate a *single* big download
> while watching a movie, at 4mbit/512k, much less torrents, which are 6
> or more.
>
> That said, most torrent clients are configurable in several ways.
>
> 1) You can limit the number of download flows to something far less
> than 6. Try 1 or 2.
>
> 2) You can typically rate limit them in the client to a lower rate
> during the day and a higher rate at night.
>
> 3) You can tell them to mark the torrents as background (QoS marking
> CS1), but that only helps on uploads vs the simple.qos script.
>
> At the router itself, you can try things like identifying torrent
> traffic via a consistent port number (if you have one) to toss it into
> the background queue , or try qos-scripts which has a layer 7 dpi
> tool.
>
>
>
>
> On Thu, Nov 20, 2014 at 6:13 AM, Dane Medic <dm70dm@gmail.com> wrote:
> > dpreed, thank you for response. I'm already using fq_codel with cerowrt
> and
> > I don't think it does what I want (or maybe I want too much :)
> >
> > So the steps I've made:
> > flashed wndr3700v2 with cerowrt 3.10.50-1 then I've measured:
> >
> > root@cerowrt:/usr/lib/CeroWrtScripts# sh betterspeedtest.sh -p
> wlan-si.net
> > -t 120
> > 2014-11-20 12:18:34 Testing against netperf.bufferbloat.net (ipv4) with
> 5
> > simultaneous sessions while pinging wlan-si.net (120 seconds in each
> > direction)
> >
> .........................................................................................................................
> >  Download:  3.78 Mbps
> >   Latency: (in msec, 119 pings, 0.00% packet loss)
> >       Min: 13.077
> >     10pct: 251.522
> >    Median: 317.851
> >       Avg: 308.497
> >     90pct: 371.033
> >       Max: 376.132
> >
> ............................................................................................................................
> >    Upload:  0.48 Mbps
> >   Latency: (in msec, 103 pings, 0.00% packet loss)
> >       Min: 12.278
> >     10pct: 12.727
> >    Median: 18.359
> >       Avg: 23.256
> >     90pct: 33.971
> >       Max: 180.303
> >
> > Then I've put these commands:
> >
> > uci set sqm.ge00.enabled=1
> > uci set sqm.ge00.download=3200
> > uci set sqm.ge00.qdisc=nfq_codel
> > uci commit sqm
> > reboot
> >
> > And another measure:
> >
> > root@cerowrt:/usr/lib/CeroWrtScripts# sh betterspeedtest.sh -p
> wlan-si.net
> > -t 120
> > 2014-11-20 12:49:05 Testing against netperf.bufferbloat.net (ipv4) with
> 5
> > simultaneous sessions while pinging wlan-si.net (120 seconds in each
> > direction)
> >
> .........................................................................................................................
> >  Download:  2.74 Mbps
> >   Latency: (in msec, 121 pings, 0.00% packet loss)
> >       Min: 12.210
> >     10pct: 13.002
> >    Median: 15.077
> >       Avg: 15.095
> >     90pct: 16.968
> >       Max: 18.599
> >
> .............................................................................................................................
> >    Upload:  0.49 Mbps
> >   Latency: (in msec, 101 pings, 0.00% packet loss)
> >       Min: 12.255
> >     10pct: 12.684
> >    Median: 16.679
> >       Avg: 23.100
> >     90pct: 34.019
> >       Max: 170.173
> >
> > The tests doesn't look bad, but the problem is I watch a video clip on
> > youtube and my sister starts torrent client, I can't watch anymore.
> >
> > Cheers
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>

[-- Attachment #2: Type: text/html, Size: 5813 bytes --]

  reply	other threads:[~2014-11-20 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 14:13 Dane Medic
2014-11-20 14:40 ` Dave Taht
2014-11-20 16:25   ` Dane Medic [this message]
2014-11-21 11:51     ` Sebastian Moeller
2014-11-21 12:04       ` Dane Medic
2014-11-21 12:17         ` Sebastian Moeller
2014-11-21 11:16 ` Sebastian Moeller
2014-11-21 11:51   ` Dane Medic
2014-11-21 12:14     ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2014-11-03  7:53 Dane Medic
2014-11-03 13:33 ` dpreed

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='CABsdH_E=oGF4xZtwnsYFzLq5=JqWu9rHbby9JMzVG4mi-g6a9g@mail.gmail.com' \
    --to=dm70dm@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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