From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: [Bloat] delay-under-load really helps diagnose real world problems
Date: Thu, 23 Apr 2015 21:55:16 +0000 [thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE9319C249E@xmb-aln-x05.cisco.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
So, I have been suffering from pseudo-random performance problems for several months. I tend to travel quite a bit, and use VPNs from several networks. I occasionally suffer from crappy web performance, but the old tools did not provide much useful info. My un-VPNed network speeds were x (where x was site specific and typically about 60 Mbps) and my VPN-ed speed were about 50 Mbps.
It seems that at one site I had occasional web surfing and Webex problems when not on the VPN, but when I got on the VPN from the same site it was OK.
At a different site, I had the opposite problem. I had sporadic problems on the raw network, but seemed to run OK on the VPN.
Well, running the new DSLReports cleared it right up. On the site where I had problems on the raw network, the report said I had ~60 Mbps of throughput - but my delay under load spiked as high as several seconds. When I fired up the VPN, the VPN became the bottleneck link at ~50 Mbps. The VPN had reasonable (not great , but reasonable) buffer sizes, and my delay was ~150ms.
On the site where I had problems on the VPN but the raw network ran OK, I found that the 50 Mbps VPN introduced several seconds of delay under load. It looks like the PoP that I use in that geography has something misconfigured with a huge buffer, and I suffer bloat when it gets congested.
I am running these things down with the various owners, which should prove to be an interesting experience.......
So, hats off to Justin!
Bill VerSteeg
[-- Attachment #2: Type: text/html, Size: 3644 bytes --]
next reply other threads:[~2015-04-23 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 21:55 Bill Ver Steeg (versteb) [this message]
2015-04-24 14:58 ` Matthew Ford
2015-04-25 2:23 ` jb
2015-04-25 2:56 ` Simon Barber
2015-04-25 4:13 ` jb
2015-04-25 4:42 ` Simon Barber
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=AE7F97DB5FEE054088D82E836BD15BE9319C249E@xmb-aln-x05.cisco.com \
--to=versteb@cisco.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