Bufferbloat FAQ page is up…

Ah, being Slashdotted is sooo much fun. In this case, it’s not the web site that was overwhelmed (since I put my blog on wordpress.com a while back), but me.  And, of course, Slashdot misspelled my name.  I’m  quite happy I didn’t try to have this on my home system, though as I think about it, it would have been a very interesting test of the broadband mitigation I did a while back (but the machine would probably have died; it was > 60,000 page views in 12 hours, and I’ve never tuned my home server). Slashdot, next time don’t Slashdot me on a Friday, so I might have a life on the weekend.

In any case, I put together a FAQ (Frequently Asked Questions) page put together in self defense.  It’s on the right sidebar of the home page. Unfortunately, this delayed several other pages I’d like to get done, like a good overview, but it does provide some better entry points to the bufferbloat postings.

3 Responses to “Bufferbloat FAQ page is up…”

  1. Luca Dionisi Says:

    The side bar is not visible if you link to a post.
    See:
    https://gettys.wordpress.com/2011/01/10/bufferbloat-faq-page-is-up/

    But don’t spend time on it!😉

  2. Ole Laursen Says:

    I spent most of my mod-points educating people at Slashdot.🙂 One of the funny ones was a guy arguing that he’d capped his own connection at 85% and thus never had any latency trouble, so what was problem supposed to be. Well, duh! Thanks for your efforts, I’m looking forward to my ISP checking and fixing their stuff. Once somebody gets a good guide written up, I’m going to forward it to them, they can upgrade the firmware remotely.

    By the way, 60.000 hits is not that much – setup a simple cache (like the one in nginx or Varnish or perhaps mod_cache), and you can get through 5000-10000 reqs/sec on not too new commodity hardware.

    • gettys Says:

      As you point out, there is problems in the ISP’s part of the network.

      But also in the home network gear. I was surprised when I caught my home router with > 8 second router, just because my wireless bandwidth was below the broadband bandwidth.

      This now happens to me much more often as I’ve upped my home service to 50/10 service, and so my bloat is usually either side of my 802.11 hop (having mitigated the Comcast hop).

      This will happen to many more people as higher broadband bandwidth deploys. FIOS folks with 20/20 or above service are also likely have this problem.

      Ironically, to get the full measure of pain, you need a nice quiet radio environment, so there isn’t much random packet drop. That’s why the FIOS wireless traces I had early on were much more confusing, and that router seemed to have set its buffers at least to limit the damage in the 1 second range. It’s at home with other routers here, in a radio very quiet area, that I get to see that bloat in its full glory.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: