Hello,

I have been working on trading system for about 3 years now and it has grown to a considerable size. I can run the strategy in the historical tester locally and acheive good results, but when I run it live, I am rarely getting into the market before the price slips < 20% of time (even though proceessing time for a tick is about 30ms). Slippage is something that I don't want to add just yet as I am making very little per trader in simulations. Regardless, I needed closer access to the market so naturally I considered the remote execution option. After compressing 3 years work down into one file so that it can be uploaded (without the @RequiresFullAccess), I am finding that this new strategy performs the same in historical tester, and works locally, but when I attempt to upload it for remote execution I get "Error in communication with strategy", and nothing else.

I can only assume that this has something to do with memory constraints. I would like to get some hard figures on the constraints we have to work within for remote deployment. Memory/cpu power. Perhaps it would be possilbe to merge multiple slots into one? Perhaps a deal sufficient memory could be arranged when I open up a live funded trading account?

Perhaps you know of some hosting near dukascopy which I could purchase which would greately reduce the RTT to market for my strategy?

How would you advise I proceed?

Best regards and thanks a million,
Ken

Currently we are allocating 32 Mb for each remote strategy. How much memory needs your strategy?