Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
What VPC configuration/specification do you use for TS?
Thanks for your reply. Timing was perfect and the comments were very helpful.
Absolutely right! It seems a D4s may be an overkill! Got same feedback from MS Azure tech support but they recommended compute optimized VM like the Fsv2. I do not think they got what I need as I had told them I only wanted to run the trades on the VMs... I still want to run all the development, optimisation etc. on my physical workstation as you said.
Anyway I am going to try them again and see what they say. But your comments were spot on and helped me to get my head around the initial configuration I need t run my trades.
Just a couple of other questions before moving on and getting this show on the road:
- where is your VM located? is the VM location in the US and close to TS servers, NYSE or COBT servers? Is that important when choosing the location?
I am based in Sydney and although am not sure location can become a concern, time zone difference can be a real killer...
Definitely will follow your previous comment on permanent solutions, from cheapest and easiest, to most and expensive difficult.
Cheers,
P.S.: on your troubles with TS, that may be due to the bugs they still have to fix on version 10. You are not the first one complaining about similar issues. Have you tried to use version 9.5 on your other account to test and compare the results? It would be good to know if that was the reason of your shutdowns...
I have a VPS that is located in NY. I had one located in Chicago too but when I compared the 2 locations with Pingplotter it was clear that the NY one ha lower ping. So I use only the location in NY now. I have also from multiple sources on other forums got the answer that it's better to have your location on the East Coast. If I am not mistaken Tradestations servers are in New Jersey. I think all data goes through those servers even if you are trading only futures.
If anyone have heard anything else please let me now but my testing has showed the server in New York works faster. In the end it's not the end of the world though as the difference i like 20-25 ms. And you won't be able to really do any scalping strategies with TS anyways.
VM location: Iowa
Location is probably not as important unless you are doing a system that has multiple trades intraday. Someone mentioned on another thread that if low-latency is an important factor, that you should be close to the trade server, which I believe for TS Securities is in Florida, not necessarily across the street from the exchange. Of course, there is no way a retail or smaller trader can compete on the level of the HFT's.
I won't revert to 9.5, as I just don't have the time to test what has been built in 10 on 9.5.
Trading: Primarily Energy but also a little Equities, Fixed Income, Metals and Crypto.
Frequency: Many times daily
Duration: Never
Posts: 5,049 since Dec 2013
Thanks Given: 4,386
Thanks Received: 10,207
Been a while since I looked at this but I think you could be both right. I think the Tradestation gateway to the internet is in NJ, but the credit check is done in FL. So when you send an order it goes
YOU >> NJ >> FL >> Chicago
So no matter how fast YOU >> NJ is, NJ >> FL >> Chicago is slow enough to make your latency slow in the execution world.
