Cool7
8 year ago
When I select server today, here is the top list I got for TESO
US West (Las Vegas - Foroquimica) 217.61 1.82
US West (Las Vegas - Versaweb) 221.15 5.49
NZ Oceania (Auckland - HDNET) - PBE → US West (Los Angeles - QudraNet 3) 216.65 14.73
NZ Oceania (Auckland - HDNET) - PBE → US West (Los Angeles - QudraNet) 218.07 14.72
US West (Las Vegas - FranTech) 254.69 2.5
US West (Fremont, CA - KLAYER) 246.3 10.9
JP Asia (Tokyo - Linode3 IDC) → US West (Los Angeles - Pump) 259.33 7.94
JP Asia (Tokyo - Linode3 IDC) → JP Asia (Tokyo - NTT 5) 258.54 9.69
US Central (Denver, CO - Mean Servers) 268.66 10.21
...
None of the Australia server is in the list. I then connect to Sydney binary lane server, it's actually response time is not bad, but in your monitor tool, it shows reponse time as 500+ms.
What is happening?
Thanks,
Simon
-
Is it still same? Not sure why at this moment. :-( It looks it's a temporary issue at somewhere though I have no idea where it's.
-
Cool7
8 year agoPath suggestion and actual performance is not always matching
-
loxch
(Forums Admin)
8 year agoIt could be an issue of mudfish server side. However what was a result of Realtime RTT graph on dashboard?
-
8 year agoCan't remember now. But it was a lot slower than 200ms. Maybe closer to 300ms. That's how I notice this.
-
8 year agoHere is another example
-
loxch
(Forums Admin)
8 year agoWhen I checked your Realtime RTT graph, it seems it began with around 200 ms but at somepoint it went to around 280 ms. Is it pointing that it was fine at the first but it becames high after some minutes? Or is it meaning that it changed to that values after setting these node combination?
-
8 year agoYes, it jumped to 280ms after I switch to that combination.
-
loxch
(Forums Admin)
8 year agoOkay. Thank you for update. Let me figure out this issue more deeply by looking into these nodes. :-)
8 year ago