cancel
Showing results for 
Search instead for 
Did you mean: 

Hub 3 / Compal CH7465-LG (TG2492LG) and CGNV4 Latency Cause

Datalink
Up to speed

Good Day Ladies and Gentlemen,

Greetings from the other side of the pond, so to speak.  Over the last few weeks I've been perusing various user forums across North America and Europe for issues related to Intel Puma 6 modem latency.  Of those forums, your Hub 3 stands out as yet another Puma 6 based modem where users see continuous latency no matter what site is used or what online game is played. Considering all of the problems that are on the go, the following information should be of interest to all Hub 3, Compal CH7465-LG and Hitron CGNV4 modem users.  There is much more to post regarding this, so this is a start, to alert VM users as to the real cause of the latency and hopefully engage the VM engineering staff, via the forum staff, with Arris.  I am surprised to see that there has been no mention on this board of users from other ISPs who are suffering the exact same issues with their modems, so, this may come as a surprise to some, and possibly old news to others.

So, the short story ........

The Hub 3 / Compal CH7465-LG (TG2492LG) & Hiton CGNV4 modems are Intel Puma 6 / 6 Media Gateway (MG) based modems.  These modems exhibit high latency to the modem and high latency thru the modem.  The latency affects all IPV4 and IPV6 protocols, so it will be seen on every internet application and game.  The basic cause is the processing of the data packets thru a CPU software based process instead of thru the hardware processor / accelerator.  It appears that a higher priority task runs periodically, causing the packet processing to halt, and then resume.  This is observed as latency in applications and in ping tests to the modem and beyond.  For the last several weeks, Hitron, along with Intel and Rogers Communications in Canada have been addressing the latency issue within the Hitron CGNxxx series modems.  To date, only the IPV4 ICMP latency has been resolved.  Although this is only one protocol, it does show that a Puma 6MG modem is capable of using the hardware processor / accelerator with good results.  Currently Rogers is waiting for further firmware updates from Hitron which should include an expanded list of resolved protocol latency issues.  For Arris modems, "Netdog" an Arris engineer indicated last week that Arris was onboard to address the issue for the Arris SB6190 modem.  That should be considered as good news for any Arris modem (read Hub 3) user as Arris should be able to port those changes over to other Puma 6/6MG modems fairly quickly.  This is not a trivial exercise and will probably take several weeks to accomplish.  Note that there is no guarantee at this point that it is possible to shift all packet processing to the hardware processor / accelerator without suffering from any packet loss side effects.  Time will tell if all of the technical issues can be resolved with the current hardware included in the Puma 6/6MG chipset.  Last night, Netdog loaded beta firmware on selected test modems on the Comcast Communications network.  As this was only done last night, it's too soon to tell what this version resolves and if it was successful or not.  Netdog has contacts with staff at Comcast, Rogers, Charter and Cox Communications to fan out beta versions and modifications for testing.  I'd say its time to add Virgin Media and/or Liberty Global to that group as well.

Recent activity:

Approx three weeks ago a DSLReports user, xymox1 started a thread where he reported high latency to an Arris SB6190 and illustrated that with numerous MultiPing plots.  This is the same latency that I and other users with Rogers communications have been dealing with for months so it came as no surprise.  As well as reporting via that thread, xymox1 took it upon himself to email several staff members at Arris, Intel, Cablelabs and others.  The result of that campaign was Netdog's announcement, last week, that Arris was fully engaged at resolving the issue.  That has led to last nights release of beta firmware, although as I indicated its too early to determine what the beta firmware resolves, if anything.


The original thread that xymox1 started is here:

https://www.dslreports.com/forum/r31079834-ALL-SB6190-is-a-terrible-modem-Intel-Puma-6-MaxLinear-mis...


Yesterday, DSLReports issued a news story covering the thread:

https://www.dslreports.com/shownews/The-Arris-SB6190-Modem-Puma-6-Chipset-Have-Some-Major-Issues-138...


Today, Arris responded:

https://www.dslreports.com/shownews/Arris-Tells-us-Its-Working-With-Intel-on-SB6190-Puma6-Problems-1...


That response was also picked by Multichannel.com

http://www.multichannel.com/news/distribution/intel-arris-working-firmware-fix-sb6190-modem/409379

This is more news likely to appear in the next few days as additional tech and news staff pick up on this issue.


Hub 3 observations:

Like many others using a Puma 6/6MG modem, Hub 3 users are experiencing latency when they ping the modem, or ping a target outside of the home, game online or use low latency applications.  The common misconception is that this is Buffer Bloat. It's not. Its most likely a case of the packet processing stopping while the CPU processes a higher priority task.  The packet processing is done via the CPU no matter what mode the modem is operating in, modem mode or router mode and no matter what IPV4 or IPV6 protocol is used.  Normally, the latency is just that, latency.  The exception are UDP packets. In this case there is latency and packet loss.  The result of that is delayed and failed DNS lookups, and poor game performance for games that use UDP for player/server comms or player/player comms.


Can this be fixed?

So far, it appears that the answer is yes.  Rogers Communications issued beta firmware to a small group of test modems in October.  This version shifted the IPV4 ICMP processing from the CPU to the hardware processor / accelerator, resulting in greatly improved performance in ping latency.  At the present time we are waiting for the next version firmware which should shift other protocols over to the hardware processor / accelerator.  That can be seen in the following post:

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/369...

The details and results of last nights beta release to the Comcast group have yet to be seen.

At this point there is enough reading to keep most staff and users busy.  My intention is to post some of the history leading up to this point and instructions on how to detect the latency and packet loss.  This is not thru the use of a BQM.  I had hoped to post this all at once but events are moving much faster than I had thought they would.  For now this should suffice to get the ball rolling.

Below is a link to a post with a couple of HrPing plots from my 32 channel modem to the connected CMTS.  This shows the latency that is observed and reflects what others have posted in this forum using Pingplotter and HrPing.

https://www.dslreports.com/forum/r31106550-

HrPing is one of the freebie applications that can be used to monitor the latency to and thru the modem. 

Pingplots with Pingplotter which show the latency from my modem to the CMTS can be found in the first two to three rows of my online image library at Rogers Communications, located below.  They are essentially what the BQM would look like if you were able to zoom into the plot to the point where you could see the individual ping spikes.  Those ping spikes are common to Puma 6 and Puma 6MG modems.

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158

 

 

 [MOD EDIT: Subject heading changed to assist community]

4,478 REPLIES 4,478

I just swapped out for a SH2ac, here's run #1

39ms : xxx
40ms : xxxx
41ms : xxxxxxx
42ms : xxxxx
43ms : xxxxxx
44ms : xxxxx
45ms : xxxx
46ms : xxxxxxxxxxxxxxxx
47ms : xxxxxxxxxxxxxxxxxxxxx
48ms : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
49ms : xxxxxxxxxxxxxxxxxxxxxxxxxx
50ms : xxxxxxxxxxxxxxxxx
51ms : xxxxxxxx
52ms : xxxxxxxx
53ms : xxxxxx
54ms : xxxxxxxxx
55ms : xxxx
56ms : x
57ms : xx
60ms : x
61ms : x
62ms : xx
67ms : xx
72ms : x
79ms : x
94ms : x
100 - 149ms :x
250 - 299ms :x

and run #2

39ms : x
40ms : xxxx
41ms : xxxxxxx
42ms : xxxxxxxxx
43ms : xxxxx
44ms : xxxxx
45ms : xxxxxxx
46ms : xxxxxxxxxxxxxxx
47ms : xxxxxxxxxxxxxxxxxxxxxxxxx
48ms : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
49ms : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
50ms : xxxxxxxxxxxxxxxxxxxxxxx
51ms : xxxxxxxxxxxxxxxx
52ms : xxx
53ms : xxxxx
54ms : x
55ms : xxx
56ms : x
58ms : x
61ms : x
66ms : x
68ms : x
69ms : x

This is mine, server 46 i am in Surrey

Run 1 6:40pm

32ms : x
33ms : x
34ms : x
35ms : xxx
36ms : xxxxx
37ms : xxxxxx
38ms : xxxxxxxxxxxxx
39ms : xxxxxxxxxxxxxxxxxxxxx
40ms : xxxxxxxxxxxxxxxxxxxxxxxxxx
41ms : xxxxxxxxxxxxxxxxxxxxxxxxxxxx
42ms : xxxxxxxxxxxxxxxxx
43ms : xxxxxxxxxxxxxxx
44ms : xxxxxxxxxxxxxx
45ms : xxxxxxxxx
46ms : xxxxxxxxxx
47ms : xxxx
48ms : xxxxx
49ms : xxxx
50ms : xx
51ms : xx
52ms : xx
54ms : xxxx
56ms : xx
57ms : x
58ms : x
59ms : x
65ms : x
68ms : x
73ms : x
76ms : x
78ms : x

Bottom colour square grid is most green a couple yellow but no red

Run 2 6:42pm

 31ms : x
32ms : x
33ms : x
34ms : xxxxxxx
35ms : xxxx
36ms : xxxxxxx
37ms : xxxxxxx
38ms : xxxxxxxxxxx
39ms : xxxxxxxxxxxxxxxxx
40ms : xxxxxxxxxxxxxxxxxx
41ms : xxxxxxxxxxxxxxxxxxxx
42ms : xxxxxxxxxxxxxxxxxxxxx
43ms : xxxxxxxxxxxxxxxxxxx
44ms : xxxxxxxxxxxxx
45ms : xxxxxxxxxxxxxxxxx
46ms : xxxxxxxxxxxxx
47ms : xxxxx
48ms : xxxxx
49ms : xxx
51ms : x
52ms : x
53ms : xx
55ms : xxx
57ms : x
63ms : x
64ms : x
71ms : x
74ms : x
250 - 299ms :x

Bottom colour square grid is mostly green and yellow with 1 red square

 

Are these results any good?

Yeah they're good James.

Not sure why my latency graphs are so high still, from the posts on her most of you when switching from hub 3 back to 2ac have no spikes at all.

My hub 3 spikes were huge when online gaming but most of the time it looked like the below

 

Hub 3 BQM 1Hub 3 BQM 1

Hub 3 BQM 2 (Very lucky i know)Hub 3 BQM 2 (Very lucky i know)

 

 

 

Hub 2ac BQM :(Hub 2ac BQM 😞

 

Not sure what the cause of this is for the randomly high spikes. I am aware that even the spikes are 20 high that doesnt mean my connection will be any better then the spikes average of 60. Just the BQM looks abnormal to me. 

 

 

Here's my change over from SH3 to SH2ac, both in modem mode with no other settings changed. The two big spikes after the change were probably when I was pegging my upload to test it.

My Broadband Ping - SH3thenSH2ac

The way I put my graph here was to 'share snapshot graph' on thinkbroadband, then copy the generated URL under the 'large graph' heading, the fourth one down. Then I switched to HTML mode here and pasted it in.

So can you see my graphs currently or not ? If so I will upload them using your method below

Previously I couldn't see your graphs, but now I can. They don't look bad -- compare to my 'before' picture! Now that was bad.

Yeah your hub 3 experience was far worse than mine but I don't get why my 2ac graph is worse than the hub 3 ? I cannot find anything else about this on the forums 😞
Maybe the latency is higher for me because I have the 2ac in router mode, and your graph afterwards is in router mode.

Are you running the BQM on the 2ac modem IP or are you running it on your aftermarket router IP?

In modem mode the router behind the modem is what gets pinged in the BQM. With my SH3 my BQM looked a little better when it was in router mode (the SH3 was then the thing responding to the pings). I haven't tried the SH2ac in router mode.

How is yours set up? Is your SH2ac in router mode (normal mode) and set to respond to pings itself?

 

My 2ac is set up in router mode as I don't have a modem and the settings are configured to accept pings