Your autotrading doesn’t require your PC to be On, am I right ?
Actually you did not really answer this. If I switch off my PC, Autotrading continues. This the normal situation. However, I know that from Australia access via IBKR’s API can be accomplished (because ProRealTime allows (or allowed) this).
Autotrading runs on the servers over here. No VPS needed for that. Also, with 400ms of latency, no matter where this VPS is, it would not help. Unless … unless that VPS is in Australia somewhere and they have a better connection that you yourself (this is imaginable). But please keep in mind, VPS does not require a VPS at all, while all other trading platforms do (AFAIK).
Does this help ?
If with manual trading the connection is lost (or can be lost) then that’s no deal of course. Pending orders or not.
You sure about those pending orders Peter …. no min distance issues or sudden poor execution with resting orders when news drops and you blow past your order – system closed?
Yes, sure. That is, min distance issues exist anyway, and is not related to your connection from home at all. Whatever means, autotrading ort manual trading, the orders rest on the PRT servers (IB or IG). Thus a pending order from autotrading is refreshed on the server, not by your PC. Notice, however, that some types of orders exist which require your PC to be On (with PRT running on it). AFAIK these orders exist only for (PRT-)IB, and they are not common at all (so much not that I would not know them by heart); (balloon ?) texts shows which they are as a precaution (“Can’t work without PRT active on your PC”).
How do you land the code on the servers ‘over there’, ‘from here’, while building ‘the code’
Your code (as far as I can tell) resides in the editor at first, which in itself will save it to the cloud (to Paris). Thus, this is already so with backtesting (press “backtest” will activate the backtest on the servers in Paris). When given to ProOrder, the same thing happens. When it runs you can shut off your PC.
The fact that a code can be kicked out (everyone’s complaint) is related to nothing, except top the broker (they are the usual cause).
Where/how the orders are routed is again not related. But it will be an interface between PRT in Paris and Euronext in Europe somewhere, or Chicago etc. (several in the US). All done by the server in Paris, auto or manual.
and it was due to retransmits and all I was doing was trying to ‘build’ an indicator ‘over there’……what a world we live in huh.
That issue remains. This may indeed possibly be solved by finding a VPS in the proper location. However, generally it will create additional round trip latency. Say A is you, C is PRT and B is the VPS (could be at the closest edge towards Paris in Australia). Then A needs to communicate back and forth to B and B will communicate back and forth with C. And that was only the way to Paris. Back will do the same. This is so severe that most probably your roundtrip latency of 400ms may turn into 2000ms. But it depends on the contentual communication. For example, with copying a file it will be like this (but it may still depend on how the file is copied – think copy vs xcopy from the Dos era – both work totally different and copy will be 10-20 times slower in the A-B-C-B-A situation).
I hope this helps you a bit or byte ?
.
