Home / Blogs

Measure Your Bufferbloat! New Browser-based Tool from DSLReports

All things come to those who wait, and bufferbloat measurement tools are no exception. When we hosted a workshop on reducing Internet latency way back in 2013, one of the identified outcomes was the need for better tools to help users understand when they had a bufferbloat problem, and now we have just such a tool from the awesome folks over at DSLReports.

Before going any further I should probably clarify what we mean by bufferbloat. Rather than going into the details of bufferbloat, what it is and what causes it, it may be simpler to think about the observable result of bufferbloat: increased latency under load. This is a measure of the additional time it takes to send data over the Internet when your link to the Internet is loaded with traffic. Today we have technology that can help to reduce that additional latency to zero, or very close to that, but it is not widely deployed. To help stimulate deployment, end-users and network engineers alike have needed a tool that quickly and simply illustrates the existence of a bufferbloat problem on any given link. Enter DSLReports new speedtest.

Go to: http://www.dslreports.com/speedtest and click the button for your Internet connection type, e.g. ‘DSL’ for ADSL lines. While the speedtest is running, you’ll see a gauge on the left-hand side of the display illustrating ‘Buffer Bloat’—you want that to stay green for most or all of the download and upload tests.

After you run the test, click the green ‘Results + Share’ button to see more detailed information. For the moment, you need to be logged in to see the more detailed latency results. There’s a ‘register’ link on each page.

The first time I ran the new tool it showed me that, although I had installed a new router on my connection recently that I knew included the latest technology to minimise latency under load, it wasn’t configured correctly.

Armed with that knowledge I tweaked the router configuration (by shaping upstream and downstream bandwidth to be just below the connection bandwidth, thereby enabling the queue management technology in the router to have an effect) and now have a much better looking set of test results.

Minimising latency under load means that I should be better able to simultaneously use my connection for downloading large files and conducting realtime interactive communications via voice and video. Why not test your link today and share your results with colleagues and friends to raise awareness of bufferbloat as an issue and to help improve our collective Internet performance experience? For more information about bufferbloat, how to test for it and what you can do about it, see the great resources over at bufferbloat.net.

This post was originally published on the Internet Society’s Internet Technology Matters blog.

By Mat Ford, Internet Technologist

Filed Under

Comments

Hi. I just tried the DSL Speedtest Thomas Narten  –  May 4, 2015 1:10 AM

Hi. I just tried the DSL Speedtest mentioned above, but it doesn’t seem to work correctly on upload. I.e., for me, it showed no delays when uploading, but when I run ping manually at the same time, I see RTTs reach 1 second.

I know I have buffer problems on the uplink side of my home modem and actually purchased a second router with sophisticated QOS settings to put in front of it in order to address the buffer problem my modem has.

Turns out ICSI Netalyzer (http://netalyzr.icsi.berkeley.edu/) also measures buffer bloat.

For me, it showed the following results. First, this is what my unmodified modem does:

We estimate your uplink as having 1200 ms of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.

Whereas if I tweak the settings of my other router (to ensure it doesn’t fill the modems buffer), I get:

We estimate your uplink as having 110 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

I can confirm that 1 sec of buffer depth is too much and you notice it immediately when the link gets saturated. Keeping the max buffer depth below 100ms keeps everything humming along much nicer.

Hi Thomas - the tool is being Mat Ford  –  May 7, 2015 12:51 PM

Hi Thomas - the tool is being actively discussed over on the bloat list (https://lists.bufferbloat.net/listinfo/bloat) and your feedback would be very welcome I'm sure.

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

DNS

Sponsored byDNIB.com

Threat Intelligence

Sponsored byWhoisXML API

New TLDs

Sponsored byRadix

IPv4 Markets

Sponsored byIPv4.Global

Brand Protection

Sponsored byCSC

Domain Names

Sponsored byVerisign

Cybersecurity

Sponsored byVerisign