Welcome to NexusFi: the best trading community on the planet, with over 150,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 -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Switched over from nt 6.5 to nt 7 last week. I had downloaded numerous indicators into nt 6.5. From
all appearance, the more numerous the indicators, the slower the performance....along with a few crashes along the way. With nt 7 I plan to refrain from adding indicators for awhile to see if the program maintains
its snappy performance. Also running onbarclose=true on all indicators as recommended. I don't know if these
issues will affect in the long term since my knowledge of these matters is quite limited This has just been my
eperience so far...it may be different with others members. Good day!
I have this running on a couple of machines and both work great. I have never had any kind of freeze or lock-up at all. My workspace is pretty simple with only 4 charts and market analyzer and 2 doms. I have never have done any backtesting or used any of the other capabilities that ninja offers so that could be it. I also run investor rt and really like that as well. The ninja chart trader is really nice.
For most indicators, the performance reduction due to setting COBC=false is negligible.
When it's an issue, it's generally because the indicator is poorly coded and performs huge numbers of operations that are totally redundant and unnecessary. We have a thread on this subject:
Anyone have any hints for optimizing C# code? Currently using Visual Studio for C#. Want to run some indicators through the process to see if there are any excessive computational issues.
NT7 is orders of magnitude better in terms of indicator processing power.
Anyone still using 6.5 at this point is just asking for trouble.
I must say that I strongly disagree. If there is a news release and you happen to trade ES you may have thousands of ticks per minute. If you trade a 1-minute chart and you set the indicator to CalculateOnBarClose = true, OnBarUpdate() will be running once per minute. However if you set it to CalculateOnBarClose = false, it may be running thousand times per minute. I believe that this has an impact on performance.
If you set several indicator to CalculateOnBarClose = false, those thousand times may freeze up NinjaTrader, even if your indicators are properly coded. Only use the setting CalculateOnBarClose = false, if you really need it.
sunny from canada
I am very happy with NT7 when i switched over from NT6.5 I only use BB; CCI and EMA-20 so my setup is very simple using candlesticks on my charts for CL;GC; and TF on 1 min charts and referring to 5 min charts for trends. NT7 has never frozen on me using CQG. happy trading
ps big mike i have learned more from this forum than anywhere else i have gone to on the internet and i thank everyone for putting great things in their posts.
However I have spent the last few weeks going through every indicator I have, and eliminating huge amounts of totally unnecessary intrabar processing built in to the great majority of them. Some of the Ninjatrader system indicators are among the most flagrant offenders.
For most indicators it's pretty easy to get an average 70% CPU load reduction just by rejecting redundant intrabar ticks that have no effect on the output value of the indicator. THEN you can start dealing with loops and function calls that are being executed on every tick but only need to run once per bar, instances of external indicators that are not explicitly defined, etc and get some huge load reductions and performance improvements.
Too bad nobody thought of doing this in the Ninjatrader 6.5 days. Now with more efficient indicators, maybe we should go back since so many people had strong emotional attachments to 6.5. Maybe we can get it to run on the Commodore 64 hardware platform. Or a Babbage Analytical Engine powered by a water wheel.
This may be the wrong place to ask this question but since we are talking about cpu useage, does anybody know whether there is a significant difference in cpu resources consumption between nt7 superdom and chart trader?
I think that neither chart trader nor superdom affect the CPU in a significant way. CPU resources are used by complex calculations performed by indicators or strategies.
