General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: Did *bufferbloat* cause the 2010 flashcrash?
Date: Fri, 7 Aug 2015 14:13:20 +0000	[thread overview]
Message-ID: <D1EA343B.10EA7E%jason_livingood@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw7jsxwVHddYHSJRfVypRFirSkcM5bQpwBHBq2w-+JZK4g@mail.gmail.com>

There are a lot of possibilities related to buffer bloat and other network
performance issues. For example, at Comcast where I work, I have come to
suspect that buffer bloat was behind the degradation of VoIP (e.g. Vonage)
while customers were using BitTorrent (which led the company down a bad
path to try to fix it but that¹s a long story).
http://www.zdnet.com/article/some-vonage-users-are-frustrated-about-comcast
-connection-quality/

JL




On 8/3/15, 5:54 AM, "Dave Taht" <dave.taht@gmail.com> wrote:

>food for thought.
>
>
>---------- Forwarded message ----------
>From: Jay Ashworth <jra@baylink.com>
>Date: Mon, Aug 3, 2015 at 5:19 AM
>Subject: Did *bufferbloat* cause the 2010 flashcrash?
>To: nanog@nanog.org
>
>
>This guy seems to think so, and his arguments seem pretty convincing
>to me, but I don't understand the financial system as well as I might.
>
>yarchive.net/blog/computers/flash_crash.html
>
>Gettys is namechecked in the piece.
>
>Cheers,
>-- jra
>--
>Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
>
>-- 
>Dave Täht
>worldwide bufferbloat report:
>http://www.dslreports.com/speedtest/results/bufferbloat
>And:
>What will it take to vastly improve wifi for everyone?
>https://plus.google.com/u/0/explore/makewififast
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat


  reply	other threads:[~2015-08-07 14:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EDA85BE-CD86-4DA9-8ED5-78500E858F79@baylink.com>
2015-08-03  9:54 ` Dave Taht
2015-08-07 14:13   ` Livingood, Jason [this message]
2015-08-07 14:23     ` Steinar H. Gunderson
2015-08-07 14:28       ` Mikael Abrahamsson
2015-08-07 14:35         ` Toke Høiland-Jørgensen
2015-08-07 14:39           ` Toke Høiland-Jørgensen
2015-08-07 14:47             ` Steinar H. Gunderson
2015-08-07 14:43       ` Sebastian Moeller
2015-08-07 14:49         ` Steinar H. Gunderson
2015-08-07 14:59           ` Toke Høiland-Jørgensen
2015-08-07 15:09             ` Jonathan Morton

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=D1EA343B.10EA7E%jason_livingood@cable.comcast.com \
    --to=jason_livingood@cable.comcast.com \
    --cc=bloat@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