Quote:
Originally Posted by Ignitionnet
Not sure that that 12 downstream change has actually worked - you're still on the standard 8 channel frequency plan.
Switch your Superhub off for a few minutes and then reactivate it, see if you get a different set of downstream channels.
|
I am not sure they meant 12 d/s channel for the shub, rather it referred to the number of available downstream channel frequencies?
Have restarted the shub2 a couple of times with no observable change. I think the problem may be in the network beyond the headend. Here are two speed tests, the first is London Namesco. This has always been a reliable fast site for me. The second is a VM site in Brentford but crucially inside the VM network:
I did this test a number of times and the VM site was always 160+Mbps and around 10ms latency. The Namesco site was always variable in speed and never near 150 plus ~3 times the latency
This seems to indicate the CMTS hop is now no longer the gating factor (where is was before). If I can get consistent headline speeds to an internal VM site but not to the internet then this raises question about the network path from the headend to the internet. It may also account for the latency difference.
Here are BQM graphs for two CMTS gateways: the first my former sotn8 gateway and the second my new sotn13 one:
You can see the base latency difference .. and this is not involving the CMTS to cable modem segment. What is strange is that these should be in the same (Sotn) headend so why the latency increase for sotn13? Weird ..