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

[Datalink]

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]

[Loui79]

Here's mine:
Gamer 200. F/W 9.1.116V

c:\iperf>iperf3.exe -c ping.online.net -p 5207 -R -u -t 62 -O 2

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 136 KBytes 1.11 Mbits/sec 43.865 ms 0/17 (0%) (omitted)
[ 4] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 23.402 ms 0/16 (0%) (omitted)
[ 4] 0.00-1.00 sec 128 KBytes 1.05 Mbits/sec 2.350 ms 0/16 (0%)
[ 4] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec 5.068 ms 0/16 (0%)
[ 4] 2.00-3.00 sec 128 KBytes 1.05 Mbits/sec 4.002 ms 0/16 (0%)
[ 4] 3.00-4.00 sec 128 KBytes 1.05 Mbits/sec 3.363 ms 0/16 (0%)
[ 4] 4.00-5.00 sec 112 KBytes 917 Kbits/sec 4.546 ms 0/14 (0%)
[ 4] 5.00-6.00 sec 144 KBytes 1.18 Mbits/sec 9.249 ms 0/18 (0%)
[ 4] 6.00-7.00 sec 112 KBytes 916 Kbits/sec 13.160 ms 0/14 (0%)
[ 4] 7.00-8.00 sec 144 KBytes 1.18 Mbits/sec 7.883 ms 0/18 (0%)
[ 4] 8.00-9.00 sec 112 KBytes 918 Kbits/sec 13.170 ms 0/14 (0%)
[ 4] 9.00-10.00 sec 144 KBytes 1.18 Mbits/sec 9.968 ms 0/18 (0%)
[ 4] 10.00-11.00 sec 112 KBytes 918 Kbits/sec 7.468 ms 0/14 (0%)
[ 4] 11.00-12.00 sec 144 KBytes 1.18 Mbits/sec 5.333 ms 0/18 (0%)
[ 4] 12.00-13.00 sec 128 KBytes 1.05 Mbits/sec 20.651 ms 0/16 (0%)
[ 4] 13.00-14.00 sec 128 KBytes 1.05 Mbits/sec 10.541 ms 0/16 (0%)
[ 4] 14.00-15.00 sec 128 KBytes 1.05 Mbits/sec 18.095 ms 0/16 (0%)
[ 4] 15.00-16.00 sec 128 KBytes 1.05 Mbits/sec 8.535 ms 0/16 (0%)
[ 4] 16.00-17.00 sec 128 KBytes 1.05 Mbits/sec 14.794 ms 0/16 (0%)
[ 4] 17.00-18.00 sec 128 KBytes 1.05 Mbits/sec 7.228 ms 0/16 (0%)
[ 4] 18.00-19.00 sec 128 KBytes 1.05 Mbits/sec 9.283 ms 0/16 (0%)
[ 4] 19.00-20.00 sec 128 KBytes 1.05 Mbits/sec 5.276 ms 0/16 (0%)
[ 4] 20.00-21.00 sec 128 KBytes 1.05 Mbits/sec 15.630 ms 0/16 (0%)
[ 4] 21.00-22.00 sec 128 KBytes 1.05 Mbits/sec 7.267 ms 0/16 (0%)
[ 4] 22.00-23.00 sec 128 KBytes 1.05 Mbits/sec 5.595 ms 0/16 (0%)
[ 4] 23.00-24.00 sec 128 KBytes 1.05 Mbits/sec 4.299 ms 0/16 (0%)
[ 4] 24.00-25.00 sec 128 KBytes 1.05 Mbits/sec 12.004 ms 0/16 (0%)
[ 4] 25.00-26.00 sec 128 KBytes 1.05 Mbits/sec 6.014 ms 0/16 (0%)
[ 4] 26.00-27.00 sec 128 KBytes 1.05 Mbits/sec 9.930 ms 0/16 (0%)
[ 4] 27.00-28.00 sec 128 KBytes 1.05 Mbits/sec 5.428 ms 0/16 (0%)
[ 4] 28.00-29.00 sec 128 KBytes 1.05 Mbits/sec 11.055 ms 0/16 (0%)
[ 4] 29.00-30.00 sec 128 KBytes 1.05 Mbits/sec 5.688 ms 0/16 (0%)
[ 4] 30.00-31.00 sec 128 KBytes 1.05 Mbits/sec 6.296 ms 0/16 (0%)
[ 4] 31.00-32.00 sec 128 KBytes 1.05 Mbits/sec 3.796 ms 0/16 (0%)
[ 4] 32.00-33.00 sec 128 KBytes 1.05 Mbits/sec 4.181 ms 0/16 (0%)
[ 4] 33.00-34.00 sec 128 KBytes 1.05 Mbits/sec 3.940 ms 0/16 (0%)
[ 4] 34.00-35.00 sec 128 KBytes 1.05 Mbits/sec 11.188 ms 0/16 (0%)
[ 4] 35.00-36.00 sec 128 KBytes 1.05 Mbits/sec 6.011 ms 0/16 (0%)
[ 4] 36.00-37.00 sec 128 KBytes 1.05 Mbits/sec 4.929 ms 0/16 (0%)
[ 4] 37.00-38.00 sec 128 KBytes 1.05 Mbits/sec 5.297 ms 0/16 (0%)
[ 4] 38.00-39.00 sec 128 KBytes 1.05 Mbits/sec 3.600 ms 0/16 (0%)
[ 4] 39.00-40.00 sec 128 KBytes 1.05 Mbits/sec 3.645 ms 0/16 (0%)
[ 4] 40.00-41.00 sec 128 KBytes 1.05 Mbits/sec 3.218 ms 0/16 (0%)
[ 4] 41.00-42.00 sec 128 KBytes 1.05 Mbits/sec 3.305 ms 0/16 (0%)
[ 4] 42.00-43.00 sec 128 KBytes 1.05 Mbits/sec 4.231 ms 0/16 (0%)
[ 4] 43.00-44.00 sec 128 KBytes 1.05 Mbits/sec 3.663 ms 0/16 (0%)
[ 4] 44.00-45.00 sec 128 KBytes 1.05 Mbits/sec 3.340 ms 0/16 (0%)
[ 4] 45.00-46.00 sec 128 KBytes 1.05 Mbits/sec 2.804 ms 0/16 (0%)
[ 4] 46.00-47.00 sec 96.0 KBytes 787 Kbits/sec 5.038 ms 0/12 (0%)
[ 4] 47.00-48.00 sec 160 KBytes 1.31 Mbits/sec 12.368 ms 0/20 (0%)
[ 4] 48.00-49.00 sec 128 KBytes 1.05 Mbits/sec 17.229 ms 0/16 (0%)
[ 4] 49.00-50.00 sec 128 KBytes 1.05 Mbits/sec 8.788 ms 0/16 (0%)
[ 4] 50.00-51.00 sec 128 KBytes 1.05 Mbits/sec 6.536 ms 0/16 (0%)
[ 4] 51.00-52.00 sec 128 KBytes 1.05 Mbits/sec 5.190 ms 0/16 (0%)
[ 4] 52.00-53.00 sec 128 KBytes 1.05 Mbits/sec 9.299 ms 0/16 (0%)
[ 4] 53.00-54.00 sec 128 KBytes 1.05 Mbits/sec 5.773 ms 0/16 (0%)
[ 4] 54.00-55.00 sec 128 KBytes 1.05 Mbits/sec 20.267 ms 0/16 (0%)
[ 4] 55.00-56.00 sec 128 KBytes 1.05 Mbits/sec 9.297 ms 0/16 (0%)
[ 4] 56.00-57.00 sec 128 KBytes 1.05 Mbits/sec 6.447 ms 0/16 (0%)
[ 4] 57.00-58.00 sec 128 KBytes 1.05 Mbits/sec 4.498 ms 0/16 (0%)
[ 4] 58.00-59.00 sec 128 KBytes 1.05 Mbits/sec 14.454 ms 0/16 (0%)
[ 4] 59.00-60.00 sec 128 KBytes 1.05 Mbits/sec 7.351 ms 0/16 (0%)
[ 4] 60.00-61.00 sec 128 KBytes 1.05 Mbits/sec 13.496 ms 0/16 (0%)
[ 4] 61.00-62.00 sec 128 KBytes 1.05 Mbits/sec 7.681 ms 0/16 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-62.00 sec 7.77 MBytes 1.05 Mbits/sec 7.681 ms 0/992 (0%)
[ 4] Sent 992 datagrams

iperf Done.

c:\iperf>iperf3.exe -c ping.online.net -p 5207 -u -t 62 -O 2

[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 152 KBytes 1.24 Mbits/sec 19 (omitted)
[ 4] 1.00-2.00 sec 136 KBytes 1.12 Mbits/sec 17 (omitted)
[ 4] 0.00-1.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 1.00-2.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 2.00-3.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 3.00-4.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 4.00-5.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 5.00-6.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 6.00-7.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 7.00-8.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 8.00-9.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 9.00-10.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 10.00-11.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 11.00-12.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 12.00-13.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 13.00-14.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 14.00-15.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 15.00-16.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 16.00-17.00 sec 128 KBytes 1.05 Mbits/sec 16
[ 4] 17.00-18.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 18.00-19.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 19.00-20.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 20.00-21.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 21.00-22.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 22.00-23.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 23.00-24.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 24.00-25.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 25.00-26.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 26.00-27.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 27.00-28.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 28.00-29.00 sec 128 KBytes 1.05 Mbits/sec 16
[ 4] 29.00-30.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 30.00-31.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 31.00-32.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 32.00-33.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 33.00-34.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 34.00-35.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 35.00-36.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 36.00-37.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 37.00-38.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 38.00-39.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 39.00-40.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 40.00-41.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 41.00-42.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 42.00-43.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 43.00-44.00 sec 136 KBytes 1.11 Mbits/sec 17
[ 4] 44.00-45.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 45.00-46.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 46.00-47.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 47.00-48.00 sec 160 KBytes 1.31 Mbits/sec 20
[ 4] 48.00-49.00 sec 136 KBytes 1.12 Mbits/sec 17
[ 4] 49.00-50.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 50.00-51.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 51.00-52.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 52.00-53.00 sec 152 KBytes 1.25 Mbits/sec 19
[ 4] 53.00-54.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 54.00-55.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 55.00-56.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 56.00-57.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 57.00-58.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 58.00-59.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 59.00-60.00 sec 144 KBytes 1.18 Mbits/sec 18
[ 4] 60.00-61.00 sec 152 KBytes 1.24 Mbits/sec 19
[ 4] 61.00-62.00 sec 136 KBytes 1.12 Mbits/sec 17
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-62.00 sec 8.70 MBytes 1.18 Mbits/sec 9.362 ms 0/1111 (0%)
[ 4] Sent 1111 datagrams

iperf Done.

[philjohn]

Ouch - 24 bonded channels? That's really bad. I'm relatively fortunate with only 20 bonded channels

[Loui79]

Yup. 24/3 since December (after 6 months of 20mbps speeds).

Definitely "Boss level broadband".... It's awesome for COD on Xbox..

[philjohn]

---

@Loui79 wrote:

Definitely "Boss level broadband".... It's awesome for COD on Xbox..

---

Well, Boss levels are meant to be hard, and VM makes gaming online hard ... so ... 😉

I'm lucky, I've always hated online gaming, too repetitive with the same maps and levels, much prefer a strong single player mode to immerse myself into. My only real issue with VM is videoconferencing when I work from home.

The one thing that hasn't been badly affected is VOIP - VM phone service wasn't available when I ordered, so I ported my BT number to SipGate and now pay no monthly line rental, and only a couple of pence per minute for international and local calls - apart from slightly longer delay than on a landline, it's not been problematic on the SH3. 

[boltedenergy]

on the latest trial firmware:
[ 4] 55.00-56.00 sec 128 KBytes 1.05 Mbits/sec 0.908 ms 0/16 (0%)
[ 4] 56.00-57.00 sec 128 KBytes 1.05 Mbits/sec 0.908 ms 0/16 (0%)
[ 4] 57.00-58.00 sec 128 KBytes 1.05 Mbits/sec 0.852 ms 0/16 (0%)
[ 4] 58.00-59.00 sec 128 KBytes 1.05 Mbits/sec 0.893 ms 0/16 (0%)
[ 4] 59.00-60.00 sec 128 KBytes 1.05 Mbits/sec 0.856 ms 0/16 (0%)
[ 4] 60.00-61.00 sec 128 KBytes 1.05 Mbits/sec 0.898 ms 0/16 (0%)
[ 4] 61.00-61.98 sec 128 KBytes 1.07 Mbits/sec 0.847 ms 0/16 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-61.98 sec 7.77 MBytes 1.05 Mbits/sec 0.847 ms 0/992 (0%)
[ 4] Sent 992 datagrams

looks pretty good actually??

[philjohn]

Well, after upgrading to Vivid 350 for the faster upload speed, it looks like I got put on .603 when my hub rebooted last night.

First impressions are positive, jitter tests definitely show less of it - in fact, UDP jitter is BETTER than when I was on a BT FTTC product - extreme left was BT 80/20 FTTC and extreme right is VM .603 firmware. The bits in between you can guess for yourself ;):

Puma 6 test also looks a lot better, and on a par with my old FTTC connection:

And finally, the obligatory BQM - ignore the spikes after the firmware went live, my network monitor runs a bunch of tests which max out the connection every 2 hours:

 And finally, the DSLReports speed test bufferbloat is showing an A, so somehow they improved that as well in the firmware. Previously I had to have SQM running on my router to get that kind of result.

[mitch84]

@philjohn

how did you do the test with the graph at the top of your post, I really want to test mine, all good here but would like to post some results.
Just don't want to have to install anything.

Did this one

[philjohn]

Sadly - it would involve installing quite a bit!

It's a custom network monitoring tool I quickly threw together, running on a Raspberry Pi - it SSH's into my router (Netgear R7800 which is running a custom OpenWRT build) and then runs iperf to do multithreaded upload/download, single threaded upload/download and UDP jitter and packet loss upstream and downstream. Chucks it into a Postgres database and then has a simple web app to chart the results.

Your Puma 6 test looks good, how is gaming?

[mitch84]

---

@philjohn wrote:

Sadly - it would involve installing quite a bit!

It's a custom network monitoring tool I quickly threw together, running on a Raspberry Pi - it SSH's into my router (Netgear R7800 which is running a custom OpenWRT build) and then runs iperf to do multithreaded upload/download, single threaded upload/download and UDP jitter and packet loss upstream and downstream. Chucks it into a Postgres database and then has a simple web app to chart the results.

Your Puma 6 test looks good, how is gaming?

---

Well I don't game online as much now days, but have played a few games recently, sea of thieves which generally is fine, a few minor occasions of lag but I think that is server side, also played a lot of BF1 the last few weeks and thats been perfect.

[philjohn]

I'm actually pretty impressed that the firmware update has all but eliminated bufferbloat, that's going to be helping lag somewhat as well.

I wonder if they tuned the TX/RX buffers on the device to be smaller ...