Just a heads up.
I would look at your machine if you are finding it hogs bandwidth - or do you have hundreds of charts up? I have a 6 year old machine with 2gb ram and a pentium chip - never gets above 80%. Your machine is a rocket ship in comparison ()
I migrated from Tradestation (5 year user) solely because NT doesn't hog bandwidth or cpu( it's about a third of tradestation in my experience)
Very occasionally it gets bogged down when the economic figs come out - but it's always to do with the API version of IB
- crashed a lot with a lot of amount of data (should be better in NT7)
- not easy as other software for configuration of charts
- lack of functionnality (I don't believe that NT7 will fill all of them) in charts, order, market analyser, instruments,...
- super DOM is confused for me (I prefer Braket trader used with IB)
- think to spend a lot of time to master the software
- programming: C# is really nice for programmers like me. You can do near anything.
I worked with metastock (was awful for programming), pro-realtime (too simple)
- you can have a complete customized interface (but spend a lot of time for this)
- strategy is on your computer and not a server (security problem)
- a big community used it
I think of NT as the "devil I know" sort of t thing. Have used it for so long that I am familar with it's quirks and short comings. I am not a coder and don't run strategies so I guess that is one of the reasons I can continue to trade comfortably using the platform. Also, I do not think I will be jumping on board the NT7 bandwagon for sometime either.
Thanks for that. I'm still considering using it on a dedicated machine, with my charts running on another machine. I don't think it's entirely fair of me to blame ninjatrader for the fact that indicators on their charts might crash. I'm sure that can happen with other platforms as well. One thing I'm looking forward to is their new DB that replaces the MS Jet db they've been using. I'm hoping this will clear up the occasional orders/trades discrepencies that are scaring me off now.
TS user here, just DLed Ninja a couple days ago for some indicators I couldn't use otherwise. So far I'm very pleased with the performance... TS can sometimes be just as bad as people say Ninja is, when it comes to bogging down your machine. Truth be told, I've really simplified my chart setup and I'm not asking Ninja to do near what TS has been asked. But I'm liking what I'm seeing.
I've been using NinjaTrader for almost a year and this is my overview opinion:
It is a quirky unstable resource hog.
You work around the quirks and make it stable by running it solo on its own machine, using minimum lookbacks and charts and indicators. This seems to be the theme of the posts here about how to avoid NT crashes. Pathetic in this techno age that we have to live with this level of performance.
One thing that has helped me improve Ninja's performance is resyncing my computer clock every minute to an atomic standard using a small program called Dimension4. Thinking Man Software - Dimension 4 v5.0
If your datafeed's time stamp doesn't match your computer time, Ninja balks (more than usual). There is a thread about this on the Ninja forum, originally thought to be a Zen-Fire problem. Frequent clock resyncing is another thing you can do to minimize Ninja's lag. ZenFire lag - NinjaTrader Support Forum
You can use the indicator on the following post to measure the lag from the time the data arrives until Ninja processes it. If your internet connection is fast and your hardware is adequate and your clock is synced, the lag is all Ninja. Put it on a 1 second chart. You'll be surprised at the delay during econ news. ZenFire lag - Page 5 - NinjaTrader Support Forum
The following 2 users say Thank You to tomgilb for this post:
Favorite Futures: Gameplay Klownbine® Trading of Globex
Posts: 1,276 since Jul 2009
Thanks: 1,227 given,
Don't Forget to REPAIR the NT6.5 Database
For anyone having problems with NT6.5, if you haven't already, REPAIR THE DATABASE. If you have strategy, ATM, and order information you want to save, be very careful to REPAIR, not RESET, the database.
Before I switched to NT7, I found that doing this every day before I shut down did seem to help a lot with performance and stability.
You will find the database repair button on the Tools>Options>Misc page.
Background: NT6.5 uses the MSJet database engine. This is the same one that powers Microsoft® Access. In routine daily use its files continually increase in size and become increasingly fragmented. Deleted table rows are marked for deletion but are not removed. The Repair process removes no longer used data, and defragments whatever remains. It does not erase any of your stored data.
If you have not done this ever, or in a while, note how long it takes for the repair process to complete. The longer it takes, the more repair work needed to be done. But I don't think it will ever take more than a couple of minutes. If you do it daily it will only take a few seconds.
The following 3 users say Thank You to Zondor for this post:
For what they charge and what they give. There is nothing like it. It is simply is the best for the money. I have some problems but nothing is perfect. I will say the problems I have with other platforms were much much worse. I have no idea what you were trying to do with it but if you are going to incidator yourself to death you never will trade well anyway. Good luck with the next one let us know how it goes. I will stick with this.