Latency between PC and wired modem

OllieOxenFree

Honorable
Jan 24, 2014
309
0
10,860
I will start off by saying that I am a competitive Counter-Strike GO player. As all of you know latency is a major factor in FPS games.

I've been battling with my ISP (TWC) for the last month including 3 separate trips to my home from technicians and countless hours on tech support. They are not denying that there is problem they just haven't figured it out yet.

The latest visit to my home include replacing all of the coax fittings in my home, a new Ethernet cable and a new router. The old router was an Arris dg860a. The new router is an Arris dg1670a.

When running a trace route or ping test with the dg860a i always received a 1ms response time between my network adapter and the modem. With the new dg1670a my response times are between 3ms and 14ms from network adapter to modem. The major ping/latency/jitter issues still have not been solved and the new modem upgrade has effectively increased my ping more so than it was before.

I have WiFi disabled on the modem. All other LAN connections have been disconnected and I have the system isolated to the supplied modem, my gaming PC, and an Ethernet cable. I also have to cables to ensure that the new cable was not the issue.


Is there any way that I can reduce this latency between my PC and the modem back to the normal 1ms?


Below are some test results to help diagnose this issue:


Pinging network adapter to ensure there is no issue there:

C:\Users\Ollie>ping -n 20 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping to modem:
C:\Users\Ollie>ping -n 20 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 12ms, Average = 5ms

Trace Route to Google.com:

C:\Users\Ollie>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:4001:c01::69]
over a maximum of 30 hops:

1 11 ms 7 ms 2 ms 2605:a000:e8c3:c300:aeb3:13ff:fe9c:ce27
2 69 ms 59 ms 19 ms 2605:a000:402:62::1
3 48 ms 77 ms 73 ms 2605:a000:0:4::2:30f
4 78 ms 94 ms 29 ms 2605:a000:0:4::2:58c
5 30 ms 78 ms 23 ms 2605:a000:0:4::38
6 45 ms 59 ms 40 ms 2001:1998:0:8::2e
7 39 ms 39 ms 39 ms 2001:1998:0:4::d1
8 41 ms 39 ms 59 ms if-ae17.0.tcore1.CT8-Chicago.ipv6.as6453.net
9 30 ms 59 ms 139 ms 2001:4860:1:1:0:3b41:0:11
10 113 ms 56 ms 69 ms 2001:4860::1:0:92e
11 43 ms 58 ms 139 ms 2001:4860::8:0:833f
12 55 ms 79 ms 59 ms 2001:4860::8:0:7893
13 84 ms 129 ms 129 ms 2001:4860::2:0:59ad
14 * * * Request timed out.
15 82 ms 73 ms 157 ms 2607:f8b0:4001:c01::69

Trace complete.

 
Solution
Motorola sb6141 or Zoom 5341J. This is assuming you have residential grade service. Both of these modems will also work with comcast in case the merger does happen.


I do not use a router. Simply a modem. The old modem supplied to me had a 1ms response time. If a different modem is the only solution to my issue, is there one that you could recommend to me that would be compatable with Time Warner Cable's current system?
 

Thank you for the info. In the meantime is there any settings I could possibly change/disable to reduce the latency within modem?
 
Both of those modems are modem/router combo devices.

If you use more then one PC you will need a router as well as a new modem.

As far as settings, you give QoS to your ocmputer but that will likley not result in any performance increase unless someone is using your wifi for netflix or torrents or something.
 


ya as stated i have system isolated to one pc and wifi disabled so sounds like I'm out of luck on that Idea...Thank you for you time though.