• State Not Answered
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 643 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 278025
Options

Feedback: A North American mirror for the Nordic Infocenter documentation would be nice

Chris Pearson

It would be nice if there was a North American mirror for the Nordic Infocenter documentation pages. Given how many connections back-and-forth something from https://infocenter.nordicsemi.com/ takes (or, at least, appears to take when viewing with Wireshark), it can take 10 to 15 seconds for a complete page to fully load. Using the index to move to another page isn't as bad, of course, but it can still be quite slow.

This is from a very high speed connection. Presumably the problem is simply distance and the speed of light in fiber optics...

  • 0

    Chris: Where are you located? (IP address?) I am in Northern NJ and haven't really see any significant delays. Yes there is a lot of chatter between the innocenter and the user. Of corse I would expect the biggest delays would be due to number of hops and their responsiveness.

  • 0 in reply to dgerman

    I'm on the west coast. 

    There are quite a few hops, but the distance adds up, too. Unfortunately, infocenter.nordicsemi.com (194.19.86.153) isn't responding to pings, but the last entry on a traceroute from here is 195.0.243.37 which is hop #21 at about 250ms. 

    Most of that seems to be distance, with about 100ms lost crossing North America, and the remainder crossing the Atlantic. Only the first 7 hops seem to be in North America, with the remainder being in Europe.

  • 0 in reply to Chris Pearson

    hmmm I get 1 more hop

     14 te0-1-0.er1.moholt.as2116.net (195.0.245.200)  118  116  117
    15  static6.banetele-cust.com (85.252.39.6)            111  113  141

    https://tools.keycdn.com/traceroute uses 11 different starting hosts (Including Dallas & San Francisco)  all but Tokyo and Sydney come in less than 200

    ]

  • 0 in reply to dgerman

    actually 3 more at the end

     13 ae6.ar1.tdjern.as2116.net (195.0.240.181)  114  110

    14  te0-1-0.er1.moholt.as2116.net (195.0.245.200)  118  116  117

  • 0 in reply to dgerman

    That's interesting. I'm quite surprised you can get ping times like that, although it's been a while since I studied networking. My time to moholt.as2116.net is a bit over double that of yours.

    Here are the numbers I'm seeing right now. This is coming from the west coast of British Columbia, with an immediate hop to Bellingham / Seattle and then across to New York. There's ~90ms just for crossing the USA (although there's an odd 20ms there...) and another ~100ms crossing the Atlantic. Obviously our data must be using different services across the Atlantic.

    There's some jitter, and on this run hop #12 comes back at 1018ms. 

    3 rd1lp-be125-1.gv.shawcable.net (64.59.161.245) 17.247 ms 17.211 ms 16.764 ms
    4 rc1wt-be40.wa.shawcable.net (66.163.68.18) 19.595 ms 19.554 ms 19.507 ms
    5 sea-b2-link.ip.twelve99.net (213.248.67.224) 19.647 ms 19.210 ms 25.389 ms
    6 nyk-bb2-link.ip.twelve99.net (62.115.119.228) 109.985 ms 107.958 ms 108.352 ms
    7 nyk-bb2-link.ip.twelve99.net (62.115.119.228) 105.688 ms 109.357 ms 108.784 ms
    8 port-b1-link.ip.twelve99.net (62.115.142.88) 20.077 ms 20.580 ms 20.515 ms
    9 oso-b2-link.ip.twelve99.net (62.115.116.116) 201.963 ms ae21.cr2.oslosda310.as2116.net (193.75.1.76) 192.546 ms 190.871 ms
    10 broadnet-ic335689-oso-b2.ip.twelve99-cust.net (62.115.162.249) 208.324 ms 191.410 ms nyk-bb2-link.ip.twelve99.net (62.115.119.228) 107.499 ms
    11 ae1.cr3.oslosda310.as2116.net (195.0.240.60) 211.919 ms ae4.cr3.fn3.as2116.net (195.0.240.150) 184.675 ms ae1.cr3.oslosda310.as2116.net (195.0.240.60) 187.047 ms
    12 kbn-bb2-link.ip.twelve99.net (80.91.254.90) 1018.579 ms ae21.cr2.oslosda310.as2116.net (193.75.1.76) 192.932 ms kbn-bb2-link.ip.twelve99.net (80.91.254.90) 1021.129 ms
    13 ae6.cr2.prinsg39.as2116.net (193.90.113.17) 217.855 ms ae5.cr2.tdjern.as2116.net (195.0.243.37) 196.332 ms oso-b2-link.ip.twelve99.net (62.115.116.116) 217.317 ms
    14 kbn-bb1-link.ip.twelve99.net (62.115.134.76) 220.691 ms broadnet-ic335689-oso-b2.ip.twelve99-cust.net (62.115.162.249) 187.789 ms 189.867 ms
    15 ae4.cr3.fn3.as2116.net (195.0.240.150) 223.245 ms ae1.cr3.oslosda310.as2116.net (195.0.240.60) 193.992 ms 191.658 ms
    16 ae21.cr2.oslosda310.as2116.net (193.75.1.76) 225.286 ms ae21.cr2.fn3.as2116.net (193.75.1.68) 194.672 ms 194.758 ms
    17 ae5.cr2.tdjern.as2116.net (195.0.243.37) 226.582 ms * *
    18 * ae1.ar1.tdjern.as2116.net (195.0.243.135) 227.589 ms *
    19 te0-1-0.er1.moholt.as2116.net (195.0.245.200) 246.363 ms * 209.060 ms
    20 static6.banetele-cust.com (85.252.39.6) 248.275 ms * 196.822 ms
    21 * ae5.cr2.tdjern.as2116.net (195.0.243.37) 243.323 ms *
    22 * * *
    23 * * *
    ... etc

Related