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)
We had cache issues that were resolved many versions ago, there should be no reason to delete your cache. The cache is designed to reduce the amount of historical data that is requested from a server thus making load time more efficient. If anyone does have memory issues, this should be escalated to our support team for further analysis.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
Can you help answer these questions from other members on NexusFi?
If you are experiencing lag during high volume times, this is usually attributable to a poorly written script/indicator. We have tools to help identify such culprit. Please reach out to our support team as they can provide further instructions to help isolate the issue and resolve your issue.
Disclosure: This communication is sent to you by NinjaTrader, LLC, a software development company which owns and supports all proprietary technology relating to and including the NinjaTrader trading platform.
Also you can open up a NinjaScript Output window and right click it to view the NinjaScript Utilization Monitor. It shows you which indicators are using the most CPU. You wouldn't believe it but rendering candlesticks use a lot of CPU/GPU.
I use the Util Monitor.... Time is not exactly correlated to memory use. I would really like to see memory allocations by indicator if possible.
BTW... I have been in PC and Networking Hell for the past 2 weeks... I finally tracked it down to a cable that had gone faulty.... I cannot explain why, but my speeds were great, but I could not download without CRC errors... I found a tool called Ping Plotter that helped me to trace it....
Sadly this response fails to address the core issue - which is that Ninjatrader lags during periods of high volatility with no third-party indicators and the absolute minimum demands put on it. This response is obfuscation, deflection and denial which regrettably is typical and frankly has become insulting, so protracted has it become. Clearly, poorly written third-party code is going to exacerbate the issue, but it is dis-ingenuous and a failure to acknowledge and take responsibility when the core problem lies with the platform.
Over on Ninja Forum there is an appalling history (with contributions from Hurley, Lancer, Bob, myself et al) showing, irrefutably:
- in high volatility, with the simplest possible workspace - 1 chart, 1 data-series, no Dom, no third-party indicators (no deflections accepted here - to re-iterate: 1 chart, 1 data-series, no fancy candle styles etc, I’ve heard them all, drop the 3rd party indicators mantra or any other, hardware, network etc)
- side-by-side comparison like-for-like with same workspace setups of Ninja and Sierra Chart both running concurrently on the same hardware/network/broker data-feed shows Sierra unperturbed during high volatility and Ninja lagging seconds behind the market.
All this is painstakingly and painfully documented on the Support Forum and yet the real nettle is persistently actively rejected let alone acknowledged or grasped.
And so it continues with this latest response.
I agree with you Bruce. I recognize all what you're saying but I must say I don't experience performance problems anymore since using naked charts or maybe with some very careful selected indicators.
Are you aware of the ' NinjaScript Utilization Monitor' as a diagnostic tool for performance issues? Select New > NinjaScript Output > Right Mouse Click 'NinjaScript Utilization Monitor'.
You can watch which part of the chart consumes most resources. I use it to see the impact of the indicators on my charts.
Once I had some indicators running smoothly but the chart was lagging, not seconds but minutes, up to 10 minutes can you believe it. One would expect that showing price on the chart would be given the highest priority (of all processes running) at all times. But no. For me that's indicative of a bad designed platform foundation/architecture. NT experts had it solved in one minute: Disable the indicators. Case closed. WTF.
I like to joke about it that NT made me a pure price action trader. But when you think about the promotions by NT of the possibilities to develop indicators it's really sad to come to the conclusion they won't work and the platform isn't suited for it. Especially when you paid a lot of money for an indicator. You know what they say: NT is for programmers, not for traders.
Now I only draw support and resistance lines on my chart. Guess what, even this is not working properly.
Since they tied the platform to a brokerage, when customers will step away from NT software they will also step away from the brokerage. Will see how long it takes. It may be they put a lot of effort in maintaining and developing the platform but I wonder if management set the right priorities.
I wonder what instrument(s) are you charting on what time frame?
Hello Mich and thanks for your input.
I’m familiar with UtilMon, however.... ‘which instruments, timeframes....’ etc.
In a TEST case: 1 workspace, 1 chart, 1 instrument, 1 Data Series 15tick RTY, candle-style OHLC, 1 indicator (ChartLagTime, very light on resources, imperceptible in use and necessary in order to test). Result: lag during Open volatility/volume
All answers to any performance-sensitive matters is a universal ‘no’. Test-bed setup, nothing else running on PC etc. No issues with network, internet etc.
Hence my trading workspace is rendered moot in this. Doubly so insofar as there was little if any difference in lag with the test single chart workspace and my trading workspace (which seems to suggest it is nothing to do with the number of instruments, data series, indicators etc. Reasoning being if it were, and lags on 1 data series alone, adding multiple instruments, data series, indicators etc would expect to see an effect. And I don’t).
And according to another user, in side-by-side like-for-like comparison Ninja lags where SC doesn’t.
I doubt that user is mis-leading nor trolling nor desire to promote SC. The same as me, want to see it acknowledged, take ownership to resolve. I hoped 22.2 may.. It hasn’t. But if that there is an issue with a barebones single chart is not being acknowledged it seems to me we’re in denial & that does not suggest it is being addressed.
I have no vested interest nor axe to grind. I purchased NT year ago so it’s hardly as if it ‘owes me anything’ other than hours in frustration. I use AMP brokerage so have other options free and paid for but would prefer to avoid a learning curve
I don’t need to enter trades at the Open, it is rare and it is rare that it has not resolved within a couple of minutes. But it happens and is reproducible on a single chart.
Good trading :-)
