From: cloneman <bufferbloat@flamingpc.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] unfixable bloat on Cable modem CODA-4680 (puma 7)
Date: Thu, 28 Mar 2019 07:00:45 -0400 [thread overview]
Message-ID: <CABQZMoLe-m2UBduYEMopFitCZnkK5NqBNbRQi+WX05CUF+u_uA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
I'm getting a weird problem with this new modem , it's Docsis 3.1
latency/jitter measured via ping is about ~300ms during download pressure
of 3 http transfers. The latency doesn't appear on synthetic bufferbloat
benchmarks, though. (dslreports ; 20ms ("A")
question: trying to figure out why I'm seeing this particular behavior, and
determine if it'd a real issue or just an anomalie with ICMP traffic
I've not seen ping do this with other modems.
Perhaps I need to try some other traffic generation/ capture tools?
[-- Attachment #2: Type: text/html, Size: 820 bytes --]
next reply other threads:[~2019-03-28 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 11:00 cloneman [this message]
2019-03-28 11:10 ` Dave Taht
2019-03-28 12:02 ` Sebastian Moeller
2019-03-28 20:44 ` cloneman
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABQZMoLe-m2UBduYEMopFitCZnkK5NqBNbRQi+WX05CUF+u_uA@mail.gmail.com \
--to=bufferbloat@flamingpc.com \
--cc=bloat@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