Would you run this strategy? 10 year DAX backtest results attached.What do you think? | Traders Hideout


futures.io - futures trading strategies, market news, trading charts and platforms


Traders Hideout


Discuss day trading practices and futures trading strategies on this forum for all markets. This forum is also for discussing and reviews for brokers, data feeds, and commercial or third party add-ons




 

Would you run this strategy? 10 year DAX backtest results attached.What do you think?

  #28 (permalink)

Administrator: Retired Backtester
Rennes France
 
Trading Experience: Advanced
Platform: NinjaTrader
Broker/Data: IB/Kinetick
Favorite Futures: Futures
 
sam028's Avatar
 
Posts: 3,555 since Jun 2009
Thanks: 3,732 given, 4,302 received


Dvdkite View Post
Hello PK 1,

Thanks again for your reply. To BE CLEAR I'm saying THANKS TO EVERY REPLY HERE FROM EVERYONE, they're helping me a lot to understand what's the best practice before go real. You're right, I like to receive some opinion from experts in automated systems before go live with real money FOR THE FIRST TIME.

About the question "why is the algo perform like this": As I said above the system is simply doing what it's supposed to do, I'm not surprised about entries and exits as they are performed as they should around VAH and VAL and POC of the previous day.

What I'm actually doing with other strategies is to leave them live all the day on MC with IQFEED and save every late evening the entries and exits on an excel file and then I compare those live results with the backtest.
And of course I'll do it with this stategy as you suggested. I'm also convinced that a minimum of incubation period is needed to see in entry levels during live simulation match with backtests entries.

Another talk is the broker, latency, datafeed.

As datafeed actually for the EUREX I'm using IQ FEED. Almost all people around here and elsewhere said that their close to the best and as far as I can see that's true.
I actually I have an italian broker WEBANK (they also give for free with the trading account the datafeed but I think that maybe is best to use IQ FEED Anyway don't you think?) and I have NO IDEA about their latency during order transmissions and executions and this is something that I have to investigate. But only a real test can show me how fast they are.
Secondary thing I have to decide if charge my account on WEBANK for algo trading or go with another broker like IB or similar. All will depends from:

1) How fast the new broker will be compared to webank (and with the good reputation of IB I think it's not easy to beat them with whatever italian bank)
2) from the margin required for the big DAX that is very high even for intraday trading.

Anyway I think that a good and clever idea would be to test it first on the MINIDAX and take a risk (and the gain) 5 time smaller... if it will perform as it should I can simply add contract if it gain enough money to cover the risk.

Actually I don't have other data subscription than for the EUREX exchange so I can test it only on dax and on the euro BUND.
I would be curious to test it with the ES and I'll do it as far as I'll find some good data of the last 10 years...

If you're don't super accurate/unfiltered tick data you should use IB. Just be sure your account is hosted in Zug Switzerland and not somewhere else. You can't use IB for large historical data but if you already have the data with IQFeed...
No idea on what Webank is using, it might be a white label trading platform and same thing for the data/order feed (I didn't recognized the trading platform).
You can have an idea of the execution latency in sending a limit order far from the current price and cancel it when it's in the book. Not 100% accurate but it will give you an idea.
IQFeed servers are in Nebraska, DAX data is coming from Frankfurt, and you're in Italy, so this combo will take time . But not a big deal on large time frame.

Success requires no deodorant! (Sun Tzu)
Follow me on Twitter Reply With Quote
The following user says Thank You to sam028 for this post: