Quote:
Originally Posted by boroboi
Pretty funny anomaly like considering every virgin connection i've seen has jitter between 10 and 20ms and max spikes from 20 to 60 and 80ms, sometimes higher... This is a network wide problem and they have to knowledge it sooner or later. We need to pressure them en-mass to fix it otherwise nothing will ever get done.
They advertise the 50mb line as perfect for games. It isn't. The jitter ruins that, and as far as im concerned that's false advertising.
|
indeed, every physical VM connection I have seen has this "anomaly". Although at varying degrees of severity, I have seen a couple which have almost no jitter off peak but still have it on peak.
the only ones that seem to not have it are some people who post on here. Although that number is declining. eg. seph used to have a perfect connection and his has gone downhill.
The ASA told them to fix it or stop advertising perfect gaming, that was some sort of pressure and that wasnt enough, VM simply instead stopped the perfect gaming ads. For this to be fixed they need a rehaul of their capacity management policy which will likely mean either higher retail prices or the scrapping of unlimited use, since both conflict with VM sales they very unlikely. The rumoured protocol immune shaping seems to have gone dead. My guess is they found it didnt work as well as they had hoped, killing speedtest speeds etc.
---------- Post added at 11:40 ---------- Previous post was at 11:35 ----------
Quote:
Originally Posted by boroboi
Yeah i've seen someone else say that too. VMMG300 will become obsolete though when they start to bond more than 4 channels.
|
yeah, I am not sure why either.
my superhub has noticeble jitter even at 4am and when my graph looks ok (not great but ok). The vmng300 used to not show such jitter unless my graph looked quite a mess. The US channel my vmng300 locks onto has been calmer for a week or so, so I am tempted to get it activated again. The risk is if the channel gets very highly utilised again tho and I wont be able to jump channels. Given its apparently queued time slots that cause jitter it would be logical to assume the modem config is somewhat different on the vmng300 with the way it queues upstream packets.
here is my graph right now, see yesterday was dodgy, then took till 4am for congestion to pretty much go away. Today it got congested before 10am but then suddenly clamed down and today so far is noticebly better than yesterday, with the graph how it is now the jitter is still noticeable at 11.42am.