I 2nd this post. Got tired of waiting and the freeze-ups were happening at the most inopportune times. On a cost basis, the cost of indicators (i.e. market profile) that are built into other software (and supported) make NT one of the more expensive options for retail. Let me know when beta has all the kinks ironed out.
Nothing in life is to be feared, it is only to be understood. Now is the time that we understand more, so that we may fear less. - Marie Curie
Last edited by fminus; March 18th, 2015 at 01:25 PM.
I am concerned about the performance issues and I am sure my support team can help, 99% of the time a client has performance issues it’s related to poorly coded or resource intensive custom indicators. Six or seven charts with system indicators will not pose a problem.
Please PM me with your contact information and I will have someone from my support team reach out and work with you so we can report back our findings in this thread.
The following 11 users say Thank You to NinjaTrader for this post:
Would be great if @freetrader would actually take advantage of this offer and then actually report the outcome back here on the thread. Not directed toward @freetrader at all, but have seen time after time, people gripe about how awful Ninja is and then it turns out the custom indicator their uncle wrote for them contains a few endless loops and their 15 year old computer with almost a full Gig of RAM just keeps freezing. One thing I know for sure... If you're not making $$$ with Ninja 7, Ninja 8 is not going to do the trick.
The following 3 users say Thank You to timefreedom for this post:
Thanks for stressing this point and I would like to add that NinjaTrader 8 will not change in this respect. If anything, with the expanded low level access for developers to take advantage of, there is more exposure to inefficient or poorly written scripts. What is different is that UI processing is distributed across all available cores.
Agreed! I know I can write Strategies and Indicators that will take down NT7 in the blink of an eye!
I am sure the new NT8 structure will make it less likely I can take out the entire program, so we will get some relief with the upgrade, but certainly, if there are problems with performance, it has been my experience that it was something I added to NT7.
I agree, however this isn't going to stop until they release NT8 and then it will be the same story waiting for NT9.
The problem is that Ninjatrader doesn't release any incremental updates/enhancements along the way. You must wait (years) on major release to get any new or enhanced features. Nearly every other platform out there releases many new features along the way in between major releases. Some do it as often as every week while others are only about once a quarter.
Many of the request throughout this thread could have been implemented along the way in NT7 and it would have prevented a lot of the complaints over the last year or so.
With that said, NT7 runs just fine for me. I am moving on to another platform because I needed the features and not because of stability issues.
Considering substantial rewrite in the NT8 (eg. the front end has changed completely - including different technology used - WindowsForms to WPF) I am willing to cut NinjaTrader some slack this time with the lack of incremental updates in NT7. Obviously the hope is that their new code base is designed with future (incremental) enhancements in mind, something we agree was missing so far. I will just wait and see.
The following 3 users say Thank You to gregid for this post:
I agree with your statement. NinjaTrader made the hard decision to jump to new technology rather than to keep pushing the same platform along and struggling. There are some architectural problems that likely exists in the NT7 which would make extension to new features more difficult. If it didn't happen now, it would have happened in the future. It was a tough decision I am sure, but it will pay off in the future.
Question about NT8, will it have more complete error reporting such that if one of my workspaces hangs during loading that it can report what chart or indicator is causing the issue? Sometimes I have issues with a workspace not loading, nothing happens in terms of errors in the log, the CPU load just goes to <1% and the workspace never completes loading. sometimes this can be caused by out dated contracts in the workspace. I would be nice to know what is causing the hang so it is easier to correct.
Also what level of stability are you expecting in the first beta release? It seems there has been a lot of time taken to test it before release, can we expect it to be quite stable? will you have a list of know bugs at beta release?