From: Bruno George Moraes <brunogm0@gmail.com>
To: Bufferbloat lists bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Issue of bloat repeatability
Date: Sat, 3 Feb 2018 18:22:03 -0200 [thread overview]
Message-ID: <CAJpr3FP-nGxK0MXQExddkLeD-mp5dbczhL6VHpGt4F9R1-TYFw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
So, i'm testing the so called "fiber" 15/1.5mbps recently installed here.
The max bloat in upload was 4800ms in the first day; Some calls later and
days of testing, last sunday there was a nice 50ms max upload.
Then came monday night, again 4xxxms, but also +200ms in download; Ok
lests call again for the ISP to fix...
Two days later, ISP guy came with his laptop and then the bufferbloat test
showed 700ms upload; Change (ethernet cable) to my laptop 4200ms, again
his 600ms; !!!
Mine is win10, latest Realtek GBE driver with 1 buffer in upload, and send
offload disabled;
???
[-- Attachment #2: Type: text/html, Size: 708 bytes --]
next reply other threads:[~2018-02-03 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 20:22 Bruno George Moraes [this message]
2018-02-04 15:36 ` Jim Gettys
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=CAJpr3FP-nGxK0MXQExddkLeD-mp5dbczhL6VHpGt4F9R1-TYFw@mail.gmail.com \
--to=brunogm0@gmail.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