Re: Bufferbloat - is it bad?
 

As far as I know they wouldn't. The queueing is simple FIFO on the CMTS cards.

Re: Bufferbloat - is it bad?
 

Both the DSLReports and TBB graphs agree. You're seeing big lag/latency from time to time. This is Bufferbloat - the undesirable latency that comes from a router or other network equipment buffering too much data.

Bufferbloat makes VoIP calls get bad, gaming gets laggy, and general web browsing gets sticky. You'll see it whenever there's traffic competing to be sent on the link. If your home router is buffering too much data, you'll see upload bloat, and if your ISP's headend/equipment is buffering too much data you'll see it on the download.

Most people think, "Oh yes, someone else is using the internet now, so things will be slow."

But it doesn't have to be - this is a solved problem. The fq_codel algorithm in OpenWrt, Linux kernels, and many commercial routers means that you can upload and download files while gaming and doing VoIP without any bad effect. (DOCSIS 3.1 cable modems also offer an effective anti-bloat system.)

As for measuring Bufferbloat, the DSLReports system uses websocket request/responses to measure the latency *during* the transfers to see how much lag is induced when transferring files. If DSLReports says there's latency, it's there.

The Bufferbloat team has a short article, "What to do about Bufferbloat?" at http://www.bufferbloat.net/projects/...ut_Bufferbloat

Re: Bufferbloat - is it bad?
 

Run a comparison between the single-threaded and multi-threaded TBB tests over ethernet.

Single threaded: http://labs.thinkbroadband.com/speed...gaUEKWiwklw392

Multi-threaded: http://labs.thinkbroadband.com/speedtest/

My bufferbloat results below for the Hub 3.0.

Single-threaded:

https://www.cableforum.co.uk/images/local/2016/01/4.jpg

Multi-threaded:

https://www.cableforum.co.uk/images/local/2016/01/5.jpg

As you can see, a big difference in downstream bufferbloat depending on number of threads/connections utilised, as expected.

You may want/need to run the tests several times, as these flash tests can suffer from spikes in data coming from the network card.

Re: Bufferbloat - is it bad?
 

These results are with HUB3 and 16 downstreams, what do you make of it and do you think my upstream looks strange, maybe it is the wrong time of the day to do it? I did speedtest.net too and it gave a far smoother download.

Single threaded.
http://www.cableforum.co.uk/board/at...1&d=1454011132

Multi threaded.
http://www.cableforum.co.uk/board/at...1&d=1454011132

Re: Bufferbloat - is it bad?
 

I don't see anything strange in the upload.

What you're seeing in the upload is the buffering in your router. On my speed test, it peaks/bursts at 14.4 meg - so that has to be into a buffer en route to TBB.

Re: Bufferbloat - is it bad?
 

I just want to leave this here. My "200mbit" connection:

https://www.cableforum.co.uk/images/local/2016/01/8.png

:(

Re: Bufferbloat - is it bad?
 

Yes, there are a few other tests.

• MUD_Wizard suggests trying single or multiple streams.
  
• You could post the link to your DSLReports tests - there's a lot of info there...
  
• For a "down in the details" test, you could run a ping test while using any of the other speed tests. Just start a ping to a well-connected host (say, google.com), then start the speed test.

Re: Bufferbloat - is it bad?
 

Re: Bufferbloat - is it bad?
 

I agree. These tests don't really mean anything except maybe for braggin' rights. The primary question is whether your network performance is good enough.

Do you get the speed you're paying for? Does it let you do anything you want, anytime you want? Does gaming work great (no lag) and do your voice calls sound OK? Is that true even when someone else is up/downloading files? If so, then you're golden. Your network is doing fine.

But... If high traffic (streaming/torrenting) screws up your connection - you get lagged out, browsing feels sticky, voip is terrible - then you need to find out why.

Most speed tests only tell about... speed. They give a quick ping time measurement, but only when the line's idle. They don't measure latency *during* the download and upload. That's why the Bufferbloat test at www.dslreports.com/speedtest is so cool. It can put numbers to the lag: if it's OK, then you can look elsewhere.

I know how to fix it - my net at home works great. It's simple, but needs a little attention.

Re: Bufferbloat - is it bad?
 

Shouldn't be. Absolutely no reason for the Hub to hold onto anything downstream, it should be getting shot of packets as soon as processing is done. Exception to that being where wireless connection is slower than broadband connection.

If the Hub is holding onto TCP traffic for excessive periods WoW and Starcraft 2 players are going to be very upset by it. If it's trying to be too clever with TCP likewise they aren't going to be happy.