nsynth.com test 1 complete

Monkey Forums/Monkey Programming/nsynth.com test 1 complete

skid(Posted 2014) [#1]
Thanks all for the help, mirrors are now stopped and I have learned heaps about providing low latency game services globally.


Hi all!

I have been developing some client server stuff.

If you have a moment please visit closest site, click connect and then click ping and post results back here.

site: http://sydney.nsynth.com
site: http://dublin.nsynth.com
site: http://virginia.nsynth.com

apk: http://nsynth.com/static/nsynth001.apk

From AK I am getting ~56ms in browser and ~35ms using plain ping from command line. For Virginia and Dublin I get ~300 and ~400 respectively.





Pharmhaus(Posted 2014) [#2]
Ping is approximately 400 for me.


skid(Posted 2014) [#3]
Will add european server next.


rIKmAN(Posted 2014) [#4]
Averages out at ~380ms for me.

I'm in England, speed is 150mb.


Raph(Posted 2014) [#5]
Around 163 for me, from California.


skid(Posted 2014) [#6]
OK, I'm going to add an EU instance, Amazon says it will be in Ireland. Hopefully will be better location for majority of users here.


Volker(Posted 2014) [#7]
360 ms from germany.


ImmutableOctet(SKNG)(Posted 2014) [#8]
Via the web-page, I get about 184ms, and I'm in Utah (United States). My internet service provider is Comcast (Unfortunately). The browser I used was Chrome (35.0.1916.153 m). Unfortunately, I can't test the APK at the moment.


slenkar(Posted 2014) [#9]
280 from kentucky


therevills(Posted 2014) [#10]
From Adelaide, South Australia:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping nsynth.com

Pinging nsynth.com [54.252.183.124] with 32 bytes of data:
Reply from 54.252.183.124: bytes=32 time=42ms TTL=54
Reply from 54.252.183.124: bytes=32 time=43ms TTL=54
Reply from 54.252.183.124: bytes=32 time=42ms TTL=54
Reply from 54.252.183.124: bytes=32 time=42ms TTL=54

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

C:\WINDOWS\system32>



nori(Posted 2014) [#11]
around 370 ms from Germany via 3G


skid(Posted 2014) [#12]
I have added links above to Dublin and Virginia instances that I now have running.

I am most interested in best ping times and if both northern hemisphere servers are required.


Roger Lockerbie(Posted 2014) [#13]
36ms for me (586k from Sydney :) )


Pharmhaus(Posted 2014) [#14]
~100 from Dublin
and ~250 from Virginia


DruggedBunny(Posted 2014) [#15]
Approx results from site...

Sydney: 308
Dublin: 40
Virginia: 105

From command line, though, Dublin and Virginia don't reply!



nsynth.com was still working after those results, and pinging its IP directly worked too.

Tried Dublin/Virginia again to no avail...


degac(Posted 2014) [#16]



Paul - Taiphoz(Posted 2014) [#17]
3180 total ping.


rIKmAN(Posted 2014) [#18]
That can't be right Paul, have you added them all together or something?


skid(Posted 2014) [#19]
Thanks everyone.

James, I don't have ICMP ping enabled on those instances yet, will let you know if that changes.


DruggedBunny(Posted 2014) [#20]
Oh... fair enough. Just assumed standard ping! At least it's not an error...


skid(Posted 2014) [#21]
ICMP requests now allowed on all three, and A records added to domain so all 3 servers have real names.


DruggedBunny(Posted 2014) [#22]
Cool, command-line update -- definitely Dublin for me, though Virginia works well too:

C:\Users\James\Desktop>ping sydney.nsynth.com

Pinging nsynth.com [54.252.183.124] with 32 bytes of data:
Reply from 54.252.183.124: bytes=32 time=300ms TTL=44
Reply from 54.252.183.124: bytes=32 time=332ms TTL=44
Reply from 54.252.183.124: bytes=32 time=296ms TTL=44
Reply from 54.252.183.124: bytes=32 time=334ms TTL=44

Ping statistics for 54.252.183.124:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 296ms, Maximum = 334ms, Average = 315ms

C:\Users\James\Desktop>ping dublin.nsynth.com

Pinging dublin.nsynth.com [54.76.187.19] with 32 bytes of data:
Reply from 54.76.187.19: bytes=32 time=41ms TTL=52
Reply from 54.76.187.19: bytes=32 time=32ms TTL=52
Reply from 54.76.187.19: bytes=32 time=32ms TTL=52
Reply from 54.76.187.19: bytes=32 time=34ms TTL=52

Ping statistics for 54.76.187.19:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 41ms, Average = 34ms

C:\Users\James\Desktop>ping virginia.nsynth.com

Pinging virginia.nsynth.com [54.86.21.64] with 32 bytes of data:
Reply from 54.86.21.64: bytes=32 time=99ms TTL=47
Reply from 54.86.21.64: bytes=32 time=98ms TTL=47
Reply from 54.86.21.64: bytes=32 time=99ms TTL=47
Reply from 54.86.21.64: bytes=32 time=98ms TTL=47

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



skid(Posted 2014) [#23]
Apparently speed of light can only go round the planet 7.5 times a second so I suppose these numbers make sense if you factor in the NSA choke points.

Less than 40ms and the server feels like it is in the same room which is nice.


degac(Posted 2014) [#24]
From the APK there is some way to change the server? It seems that it point always to nsynth.com while I would to test Dublin node.


erebel55(Posted 2014) [#25]
Sydney: 2265ms
Dublin: 1386ms
Virginia: 566ms


Lindsay(Posted 2014) [#26]
I'm in Sydney, I get 10 pings in 401ms.


skid(Posted 2014) [#27]
holy crap, dublin.nsynth.com just got owned by Mega Fortune, who the fduck???


StoneFaceEXE(Posted 2014) [#28]
Task: ping nsynth.com
Result: 446 ms (Average)
Location: Moscow
Speed: 30 MegaBIT

I have no idea what I just did though.)