Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Low Latency / Minimum Number of Hops
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Low Latency / Minimum Number of Hops

Mahfuz_SS_EHLMahfuz_SS_EHL Host Rep, Veteran

Hi,

I'm going to move My cPanel Server from One Location to Another. Current Location is Las Vegas, Nevada in FiberHub. From Bangladesh, it gets around 290 ms Ping Response & 11 Hops completed in total connection by Tracerouting.

Thinking to move it to Amsterdam, NL in Phoenix Nap. From Bangladesh, it's getting around 180-190 ms but it takes 17 Hops in Total Connection.

Which one do you prefer based on Network Connection ?? Which is Better ?? Low Latency / Minimum Number of Connections !

Regards,
Mahfuz.

Comments

  • Depends on the scenario. For gaming that requires packets that need to be transmitted quickly, minimum hops are best.

  • @Mahfuz_SS_EHL said:
    Hi,

    I'm going to move My cPanel Server from One Location to Another...

    Is this a VM or dedi? If VM, why not move it to DO Singapore?

  • rm_rm_ IPv6 Advocate, Veteran
    edited October 2014

    said: Low Latency / Minimum Number of Hops

    Number of hops doesn't affect your latency in any way, it's just a matter of how different carrier networks are configured. Some by the use of MPLS or other L2 tech will show only the first and the last points as you travel their network, some will show every city along the way on the trace.
    So you should only look at the latency (in ms) alone.

    0xdragon said: For gaming that requires packets that need to be transmitted quickly, minimum hops are best.

    ...and this makes me wonder if you maybe have a pastime of going around forums leaving responses that'd be absolutely shockingly retarded on purpose, just to see the reaction. But just in case you were serious, can you confirm, in the above scenario you would choose the one that gives 290ms ping (w/11 hops), over 180ms ping (w/17 hops)?

    Thanked by 3rds100 coolice Pwner
  • rm_ said: But just in case you were serious, can you confirm, in the above scenario you would choose the one that gives 290ms ping (w/11 hops), over 180ms ping (w/17 hops)?

    I second this.

    The number of hops can be an indicator for latency but the only important factor is - surprise - latency. A connection with a latency of 50ms and a trillion hops will always be better than one with 150ms and three hops.

  • Mahfuz_SS_EHLMahfuz_SS_EHL Host Rep, Veteran

    Then, going with Latency !

  • HSNHSN Member

    The lower lattency will work better for you, however can you place your trace record from bangladesh to nl? I bet the most hops are cognet or he? Right?

  • emgemg Veteran
    edited October 2014

    I agree with those who say that latency is more critical than hop count.

    If your packets got routed to the moon and then directly to your destination, it would be only two hops, but the ping response time would be roughly 5000 ms. (5 seconds)

    (Latency for Mars would be so long that you couldn't establish an ordinary TCP connection without adjusting timeout values. I had not given it much thought before, but I just looked it up. Not surprisingly, our interplanetary rovers and orbiters rely on special network stacks. They can't use ordinary TCP/IP.)

  • Based in Phnom Penh, just moved a vps/sites from US West Coast to DO Singapore.
    Latency/ping from LA was 190ms(SEATTLE 235ms) but now 50 ms from Singapore.
    There is no going back.

  • Mahfuz_SS_EHLMahfuz_SS_EHL Host Rep, Veteran
    edited October 2014

    DIGITAL OCEAN AMS-1:

    Tracing route to speedtest-ams1.digitalocean.com [146.185.176.179]
    over a maximum of 30 hops:
    
      1    1 ms     1 ms    1 ms  196.168.1.1 
      2     1 ms    1 ms     1 ms  103.253.47.21.deltainfocom.com [103.253.47.21] 
      3     2 ms     1 ms     1 ms  aggr-g0-0-3.deltainfocom.com [103.31.176.1] 
      4     1 ms     1 ms     1 ms  core-asr-g0-2-1.deltainfocom.com [103.15.164.197] 
      5    48 ms    48 ms    48 ms  202.56.246.113 
      6   178 ms   178 ms   180 ms  182.79.255.78 
      7   171 ms   171 ms   171 ms  ldn-b2-link.telia.net [213.248.71.17] 
      8   172 ms   171 ms   171 ms  ldn-bb2-link.telia.net [80.91.249.177] 
      9   176 ms   177 ms   178 ms  adm-bb4-link.telia.net [213.155.136.91] 
     10   205 ms   176 ms   177 ms  adm-b4-link.telia.net [213.155.137.187] 
     11   178 ms   175 ms   176 ms  digitalocean-ic-302452-adm-b4.c.telia.net [62.115.34.22] 
     12   292 ms   295 ms   292 ms  146.185.176.179 
    
    Trace complete.
    

    DIGITAL OCEAN AMS-2:

    Tracing route to speedtest-ams2.digitalocean.com [95.85.7.154]
    over a maximum of 30 hops:
    
      1    1 ms    1 ms    1 ms  196.168.1.1 
      2     1 ms     1 ms    1 ms  103.253.47.21.deltainfocom.com [103.253.47.21] 
      3     1 ms     1 ms     1 ms  aggr-g0-0-3.deltainfocom.com [103.31.176.1] 
      4     1 ms     1 ms     1 ms  core-asr-g0-2-2.deltainfocom.com [103.15.164.201] 
      5    48 ms    48 ms    48 ms  202.56.246.113 
      6   178 ms   178 ms   200 ms  125.62.187.214 
      7   185 ms   205 ms   185 ms  digitalocean.telecity5.nl-ix.net [193.239.117.100] 
      8   193 ms   187 ms   186 ms  95.85.0.238 
      9   177 ms   176 ms   176 ms  95.85.7.154 
    
    Trace complete.
    

    HostDime NL:

    Tracing route to ovz-nl1.hostdime.nl [109.73.174.10]
    over a maximum of 30 hops:
    
      1    1 ms    1 ms     1 ms  196.168.1.1 
      2     1 ms     1 ms     1 ms  103.253.47.21.deltainfocom.com [103.253.47.21] 
      3     1 ms     1 ms    1 ms  aggr-g0-0-3.deltainfocom.com [103.31.176.1] 
      4     1 ms     1 ms     1 ms  core-g0-1-1.deltainfocom.com [103.15.164.5] 
      5    52 ms    48 ms    48 ms  202.56.246.113 
      6   179 ms   180 ms   185 ms  182.79.245.37 
      7   186 ms   184 ms   197 ms  10ge.linx-jnpr.th-n.i3d.net [195.66.225.146] 
      8   186 ms   193 ms   186 ms  20ge.cr1-lr0.smartdc.rtd.i3d.net [109.200.218.173] 
      9   285 ms   186 ms   198 ms  80ge.br2-cr1.smartdc.rtd.i3d.net [188.122.95.84] 
     10   186 ms   187 ms   186 ms  ovz-nl1.hostdime.nl [109.73.174.10] 
    
    Trace complete.
    

    SingleHop NL:

    Tracing route to vmware-hypervisor-infrastructure-node1.ams01.singlehop.net [198.20.98.2]
    over a maximum of 30 hops:
    
      1    1 ms    1 ms     1 ms  196.168.1.1 
      2     1 ms    1 ms    1 ms  103.253.47.21.deltainfocom.com [103.253.47.21] 
      3     2 ms     2 ms     1 ms  aggr-g0-0-3.deltainfocom.com [103.31.176.1] 
      4     1 ms     6 ms     4 ms  core-g0-1-1.deltainfocom.com [103.15.164.5] 
      5     1 ms     1 ms     1 ms  103.7.249.53 
      6    62 ms    62 ms   116 ms  ix-2-3-2-0.tcore2.CXR-Chennai.as6453.net [180.87.37.57] 
      7   184 ms   191 ms   175 ms  if-3-3.tcore1.CXR-Chennai.as6453.net [180.87.36.5] 
      8   177 ms   174 ms   174 ms  if-7-2.tcore1.MLV-Mumbai.as6453.net [180.87.36.33] 
      9     *        *        *     Request timed out.
     10   175 ms   174 ms   174 ms  if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6] 
     11   175 ms   175 ms   175 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17] 
     12   177 ms   177 ms   180 ms  64.125.14.57 
     13   182 ms   182 ms   182 ms  ae4.mpr2.cdg12.fr.above.net [64.125.22.166] 
     14   181 ms   181 ms   182 ms  ae3.mpr2.lhr2.uk.above.net [64.125.32.98] 
     15   181 ms   182 ms   181 ms  64.125.28.22 
     16   186 ms   191 ms   186 ms  ae9.cr1.ams10.nl.above.net [64.125.28.241] 
     17   194 ms   188 ms   188 ms  ae8.mpr1.ams10.nl.above.net [64.125.26.158] 
     18   185 ms   184 ms   184 ms  ae2.mpr1.ams13.nl.above.net [64.125.20.50] 
     19   193 ms   192 ms   192 ms  94.31.42.122.IPYX-073272-001-ZYO.above.net [94.31.42.122] 
     20   189 ms   190 ms   189 ms  vmware-hypervisor-infrastructure-node1.ams01.singlehop.net [198.20.98.2] 
    
    Trace complete.
    

    @HSN

  • HSNHSN Member

    @Mahfuz_SS_EHL

    what I am seeing is that "DIGITAL OCEAN AMS-2" would be better for you. Lower latency and less hops

Sign In or Register to comment.