Superhub : Hub 3 channels?

[Ken W]

Originally Posted by Sephiroth

As per what SnoopZ said, Ken.

I will have to make shore I don't for a factory reset.

[Synthetic]

Anyone not on the trial got this yet? Wondering if it makes a difference to the latency spikes some have seen with it...

[SnoopZ]

Still trial only, ignore all that yellow you see on the TBB graph when on 16 channels, we had a similar issue on the SH2ac when released and they fixed that with firmware as i think it was just reporting it but it didn't affect the connection in anyway if i remember.

I know in my case since moving to 16 channels and getting all that huge yellow on my graph it didn't make the connection any worse or the ping any different than when i was on 8 channels.

[Synthetic]

I was slightly worried about that, although I can't setup a TBB graph yet until they give us the ability to enable pings in router mode.

Gaming seems a bit laggy, not sure if it's actual latency or something to do with the NAT issues.

[SnoopZ]

If you turn the firewall off you can setup a TBB, hopefully you would be using a software firewall too if you did that.

I could be wrong in my thoughts though, regarding all that yellow but from my below graphs it all looks fine to be even though there is all that yellow, which doesn't seem to affect pingtest.net



[img]Download Failed (1)[/img]

[MUD_Wizard]

Originally Posted by SnoopZ

Still trial only, ignore all that yellow you see on the TBB graph when on 16 channels, we had a similar issue on the SH2ac when released and they fixed that with firmware as i think it was just reporting it but it didn't affect the connection in anyway if i remember.

I know in my case since moving to 16 channels and getting all that huge yellow on my graph it didn't make the connection any worse or the ping any different than when i was on 8 channels.

Bear in mind that the Thinkbroadband BQM graph samples 100 seconds worth of pings. The minimum, average and maximum are calculated from that.

So on the maximum you could have 99 seconds of 20ms pings and one second (or fraction of a second) of 100ms ping, and that would produce the yellow spikes in the graph you see.

The Superhub2/2ac also produced similar levels of 100ms spikes, though not as often. If you keep in mind that someone on 16 channels has two sets of 8 channels, then two sets of 100ms spikes would look like the graph we're seeing.



If you run a continuous ping to google you will notice a few 100ms pings mixed in with 99% around 20ms.

The latency shown on speedtest.net and pingtest.net tests aren't maximum latency, but average latency (represented in blue on the BQM). Which is why it won't show up there.

[SnoopZ]

So the Hub3 has a real problem then in your opinion?

If so i hope it can be fixed in firmware.

[MUD_Wizard]

Originally Posted by SnoopZ

So the Hub3 has a real problem then in your opinion?

If so i hope it can be fixed in firmware.

No, it's what I expected for 16 channels.

People who've shown BQM graphs from Hub 3's on 8 channels looks roughly the same as a SH2/2ac BQM.

[Sephiroth]

The Hub 3 can't be said to have a "real problem" unless you have a real problem with stuff you're doing that isn't affected by local contention.

It's exactly as Muddie says about the yellow showing the solitary maximum ping return time. The early firmware in the SH2ac had larger yellow than the current firmware.

Do remember that the Hub 3 modem mode is a bridge mode whereby all that has happened is NAT is disabled in the Hub 3 which means that there is no other route than the single port through which data can flow. So if, for example, every so many milliseconds the trial firmware is "doing stuff", perhaps sending diagnostics out, and I have no knowledge that this is the case, then it would expolain the high yellow.

[Synthetic]

My main problem with the sh3 is the lack of upnp / Nat for gaming, and I find the WiFi range pretty poor, might just be me expecting too much though....

[SnoopZ]

Upnp will get fixed eventually but all these fixes will come in drips and drabs, I just wish it was a speedy process.

[mmm]

Originally Posted by MUD_Wizard

If you run a continuous ping to google you will notice a few 100ms pings mixed in with 99% around 20ms.

You don't need to go out to google, can see ping spikes from wired lan to SH3, seems to occasionally be too busy to bother responding quicky - has more important things to do?

[Ignitionnet]

Originally Posted by MUD_Wizard

Bear in mind that the Thinkbroadband BQM graph samples 100 seconds worth of pings. The minimum, average and maximum are calculated from that.

So on the maximum you could have 99 seconds of 20ms pings and one second (or fraction of a second) of 100ms ping, and that would produce the yellow spikes in the graph you see.

The Superhub2/2ac also produced similar levels of 100ms spikes, though not as often. If you keep in mind that someone on 16 channels has two sets of 8 channels, then two sets of 100ms spikes would look like the graph we're seeing.

If you run a continuous ping to google you will notice a few 100ms pings mixed in with 99% around 20ms.

The latency shown on speedtest.net and pingtest.net tests aren't maximum latency, but average latency (represented in blue on the BQM). Which is why it won't show up there.

This confuses me. The jitter doesn't come from downstream, it comes from upstream. Virgin Media's measured jitter downstream is actually pretty good.

Adding more channels should help with any latency issues on downstream, not hinder them. They aren't considered 2 blocks of 8 channels but 1 block of 16 and the scheduler should use the least loaded channel when deciding which channel to send traffic down. The scheduler has full control over the loading of channels and can easily ensure no channel sees 100ms of queuing.

Sure this isn't just something alongside the same lines as why people are reporting higher baseline minimum latency on this kit, it's a little tardy about responding with the existing firmware?

Nothing wrong with that, mind you.

---------- Post added at 01:12 ---------- Previous post was at 01:10 ----------

Originally Posted by MUD_Wizard

No, it's what I expected for 16 channels.

People who've shown BQM graphs from Hub 3's on 8 channels looks roughly the same as a SH2/2ac BQM.

If that's the case there are definitely some issues to fix. That really shouldn't happen.

[Synthetic]

Originally Posted by SnoopZ

Upnp will get fixed eventually but all these fixes will come in drips and drabs, I just wish it was a speedy process.

Especially for customers who aren't trialists and have no idea what's going on

Last time I'll complain about that, I promise haha