Welcome to NexusFi: the best trading community on the planet, with over 200,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 -- discounts are available after registering.
-- The NexusFi team
(If you already have an account, login at the top of the page)
I was a long-time user of Trade Station and became fairly proficient at coding "Easy" language. I switched to Ninja because I liked the look of their charts and I was frustrated with TradeStation's way of back testing, where a touch at a price counted as a definite fill. This is very unrealistic for a scalping strategy.
Anyway I've finally gotten fairly decent at programming strategies in Ninja, but I find that Ninja hangs up very easily if I'm back testing over more than 2 or 3 weeks. TradeStation was much more stable in this regard IMO.
Anybody have similar experience? Is there a way to improve Ninja's performance?
rsi77
Can you help answer these questions from other members on NexusFi?
2 or 3 weeks, but with which time frame, how many bars ?
I've backtested some strategies with more than 1.000k without stability issues (it's just quite long ).
Site Administrator Developer Swing Trader R.I.P. 1977-2026
Experience: Advanced
Platform: Custom solution
Broker: IBKR
Trading: Stocks & Futures
Frequency: Every few days
Duration: Weeks
Posts: 50,669 since Jun 2009
Thanks Given: 33,669
Thanks Received: 102,586
rsi77,
If you are using anything other than minute data, then almost always the issue is the .NET memory limits of Ninja 6.5. There is a hack (here) but won't work for most people due to the complexity.
You'll probably just need to wait for NT7 if this is what you're seeing. You can know for sure by checking taskmgr and seeing if it is exceeding about 1.3-1.5GB. If so, it's the memory cap issue.
You also need to keep very close eyes on the Log tab inside control panel.
Yep, I use tick and volume charts for most of my testing. Josh at Ninja also said the NT 7.0 has better memory handling capability than the present version and that this should help with the choking I so often experience. I would use your hack but am not running XP64. Thanks for the info anyway. Oh well. I hope 7 is out soon.
).
