My example was hypothetical. Seems like pingtest.net auto selects the target ping receipient for you. Usually, it will pick somewhere close to the location of the tester. I would get 11ms eveytime.
I also ran speed tests from dslreports.org (sorry,i am not allowed to post a link yet)
I can choose which city to test against. (NY, LA, Chicago, Toronto, etc) I get significantly different results from each city.
Let me see... From NY to NY : 15ms / From NY to NJ : 17ms / From NY to Chicago : 25ms / From NY to LA : 95ms/ NY to Toronto : 122ms
I am using zenfire and they are in chicago. I was thinking if I am to host my trading hardware in Chicago as opposed to New York. How much faster will the respond time be? or does it matter at all?
depending on your trading style if just scalping 11 ms is more than enough if bot trading you have to co-locate better at exchange building using it internal network.
Pings to different cities shows different results simple because of distance as well as different cities has different "infrastructure quality".
what I'm looking now is software which helps to modify your channel, reserve it solely for certain data transmission and certain IP addresses, cutting/minimizing all other functionality and IP address, that also helps to maintain better stability of channel during usual peak times of social using of internet.
Your ping time to your broker is the only realistic measurement. If your responds time to your broker is +1000ms. , you can forget if you get ping response from pingtest.net at <10ms. Local ping time is meaningless.
Zenfire API will connect to 188.8.131.52 for ordering and market data. Sadly, this IP does not respond to ping.
Anyone know a good ip to ping at zenfire?
Zenfire, if you are reading this... please give us a IP for benchmark purposes!
In my other life I'm a Network Architect, and I have designed/supported many sites in the Asian timezones from North America.
200-275ms round trip ping times between NZ and Chicago is typical. There is little that can be done to improve that.
It's not a matter of speed, it's simply the time it takes light/electrons to travel that distance thru copper or glass. ... The latency would be similar on a large dedicated circuit vs the Internet.
Who'd-a-thunk we'd be dealing with limitations in the speed of light in our day and age, eh?
So.. you are going to be at least 1 second behind the exchanges...
250ms to deliver the chart/quote data
250ms to send the order
250ms to acknowledge the order
250ms to ... whatever ....
250ms is 1/4 of a second..It doesn't take many interactions to really start to add up.
Probably not well suited to any trading styles that require sub-second interactions.
The following 2 users say Thank You to zoltran for this post: