Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Cerowrt-devel] quick survey: actual drop and mark stats from live sqm-scripts + fq_codel'd networks?
Date: Tue, 12 May 2015 09:15:29 -0700	[thread overview]
Message-ID: <CAA93jw49VhOQEzyBgFJVLMBKT9TXACLSpAi9+8YFb3kqarUMLQ@mail.gmail.com> (raw)

I am curious as to the drop and mark statistics for those actively
using their networks,
but NOT obsessively testing dslreports' speedtest as I have been :),
over the course of days.

A cron job running once an hour would work, but snmp polling with
mrtg, parsing the tc output would be better.

But a quick survey would be interesting, if you could dump your

uptime
tc -s qdisc show dev whatever
tc -s qdisc show dev your_inbound_ifb_device

here?

and also check to see if you are getting drops or marks on your core
wifi interfaces. For example a great deal of the dropping behavior for
me has moved to wifi over the last year (as we upgraded from 20mbit
down to 60 or 110mbit down), particularly on my longer distance links
but also on links that have very good same room connectivity.

example wifi interface (6 days of traffic)

qdisc fq_codel 30: parent 1:3 limit 1000p flows 1024 quantum 300
target 5.0ms interval 100.0ms ecn
 Sent 3409244008 bytes 3400248 pkt (dropped 487, overlimits 0 requeues 2703)
 backlog 0b 0p requeues 2703
  maxpacket 1514 drop_overlimit 0 new_flow_count 1637 ecn_mark 0
  new_flows_len 0 old_flows_len 0


this is the same routers external interface (60mbit downlink) (yes, I
deployed ecn on every box I could)


qdisc fq_codel 120: parent 1:12 limit 1001p flows 1024 quantum 1500
target 5.0ms interval 100.0ms ecn

 Sent 741392066 bytes 8765559 pkt (dropped 0, overlimits 0 requeues 0)

 backlog 0b 0p requeues 0

  maxpacket 1514 drop_overlimit 0 new_flow_count 2815747 ecn_mark 0

  new_flows_len 1 old_flows_len 1

qdisc fq_codel 130: parent 1:13 limit 1001p flows 1024 quantum 300
target 5.0ms interval 100.0ms ecn

 Sent 362010241205 bytes 268428951 pkt (dropped 28391, overlimits 0 requeues 0)

 backlog 0b 0p requeues 0

  maxpacket 1514 drop_overlimit 0 new_flow_count 34382791 ecn_mark 238

  new_flows_len 1 old_flows_len 3

tc -s qdisc show dev ge00 (uplink, 10mbit)

qdisc fq_codel 120: parent 1:12 limit 1001p flows 1024 quantum 300
target 5.0ms interval 100.0ms ecn

 Sent 19054721473 bytes 141364936 pkt (dropped 2251, overlimits 0 requeues 0)

 backlog 0b 0p requeues 0

  maxpacket 1514 drop_overlimit 29 new_flow_count 37418891 ecn_mark 15593

  new_flows_len 0 old_flows_len 2




-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

             reply	other threads:[~2015-05-12 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 16:15 Dave Taht [this message]
2015-05-13  0:24 ` David Personette

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=CAA93jw49VhOQEzyBgFJVLMBKT9TXACLSpAi9+8YFb3kqarUMLQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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