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)
I was wrong. NinjaTrader is still "Not responding" and using excessive CPU during these times. This is with all stock bar types and only a few custom indicators that are very basic. And this occurs even when none are enabled/in use.
My only guess is at some point they (or a third party) made a change to the windowing code. Possibly threading related? Only guessing.
(1) In your current workspace, how many charts do you have open for how many instruments?
(2) Are other workspaces running in the background?
(3) Are you using custom bar types (free stuff or third party, not supplied with NinjaTrader)?
(4) Are you using custom indicators (free stuff or third party indicators, not supplied with NinjaTrader)?
(5) How many of your indicators have you set to "CalculateOnBarClose" = "false"?
(6) Did you change the display update interval of your chart to a value smaller than 500 msec?
I would take the PC system back to naked, or as close as possible. That means disable Windows Auto-Update (background process) and any other background updater (browser, Java, etc), Anti-virus (after scanning for malware of course), and start with a fresh set of charts - I have found that NT will duplicate indicators on multi-symbol charts at random (even the same symbol but different chart types/timeframes). Since the duplicates are all in their original panels, you won't know unless there is a visual clue (like the ToolbarShortcut on the chart). They will just eat up CPU for nothing.
Finally, on any indicator set to CalcOnBarClose = false that is not Volume or TickCount based, I would insert a LastPrice = Close[0] variable, and if the last price did not change, issue a "return;" to shortcircuit the calcs.
I think this is possible via a setting in NT8, but for NT7, its a workaround.
Also run Speedtest.net to check on your internet connection.
Sorry folks I meant to update this thread after resolving the issue yesterday but I got sidetracked.
So get this...
The issue was that NT would become basically unusable from "Not Responding" (excessive CPU) after a minute or two after connecting to MB Trading (no charts opened, no workspaces, no strategies running, NOTHING). All other apps (Chrome, Firefox) were working fine. I normally do not reboot because I have so much going on.
I reinstalled NT 7 (a couple times), reinstalled MBTrading Navigator, contacted NT Support. They couldn't reproduce the issue.
So I decided to install a few Windows security updates and install an optional .NET v3.5 update. I reboot... and damn if that doesn't fix it. I think I had grown comfortable with Windows 7 working "normal" for weeks/months on end without rebooting, but this changed my mind. I have no idea why rebooting would fix a single application (NT or MB Tradings Navigator) but it did. Maybe the .NET v3.5 update will help with the issue going forward, but I can only guess.
My guess is that Windows was doing something funky. This is Windows 7 with all important updates applied.
As @Fat Tails says, the .NET upgrade may have fixed it.
But I would also always reboot; I reboot Windows 7 every day. Very often as the day wears on things start to slow down as I use up available resources (opening too many windows, etc.) Closing applications may not fix it -- something apparently doesn't always get freed up even though it should -- but rebooting always does.
And if I have no problems, I just reboot anyway at night. Still a good practice with Windows, I think.
When one door closes, another opens.
-- Cervantes, Don Quixote
I'm pretty sure I was already running .NET v3.5 ... I think its included in Windows 7.
The update (KB2836943) was released in Sept 2013 and is for .NET 3.5.1 on Windows 7 SP1 and Windows Server 2008 R2 SP1.
I'm guessing the reboot fixed it, but like I said, with Windows 7 SP1, I rarely notice any performance issue from not rebooting and in this case only NT was affected so it may be .NET specific (if Chrome/Firefox don't use .NET).
I'm a unix guy by trade so normally I'd rather not reboot except when necessary. Next time I'll reboot first, just like the old XP days.
"Just like the old XP days.... " Huh. I've used Windows (by trade), on desktops since 3.0 (or whatever it was) and on servers since whenever they had server versions.... man, I always reboot it. Daily.
Never used unix, so I don't know about that universe, but I do know Windows.... it just is just better when you reboot. Yes, it does deserve the sarcastic icon, but a lot of the world runs on it, for better or worse.
Bob.
When one door closes, another opens.
-- Cervantes, Don Quixote
Reality is, for apps that need to be available 24 hours, its just not always possible or desired to reboot daily. This is where Unix has always reigned supreme with some machines being up for years.
My experience with XP was exactly as yours, reboot often. But I've had some hope with Windows 7+ and 2008+ that rebooting regularly was no longer necessary. So far, unfortunately, I've proven to myself that it is still needed to fix whatever problem I ran into (possibly .NET v3 specific?). Hopefully NT v8 and .NET v4 will really make a difference stability wise.
Regarding the use of the "sarcastic" smilie, I think its kinda mislabeled.. I normally just use it as I see it: having a good laugh, I don't intend it to be viewed as I'm being sarcastic even though someone might reasonably think this.
Current Windows servers can stay up for a long time; it has gotten to be pretty reliable. I still would want to have a Windows box rebooted when I can. I have had web servers up continuously for a long time so things are much better. Fortunately, I am no longer managing IT, and, while that means I'm not necessarily up to date any more, it also means I don't have to be . All I've done in a while is programming, and now essentially trading...
I wish that I had worked with Unix when I was in that business, but you go with the market (job) opportunities that you have.
I didn't really mean the "sarcastic" thing in a mean way, it's just a pointed laugh.
I do reboot Windows 7, and I find it helps with Ninja. I'm not sure if they have a problem or if Windows does, but my guess is that rebooting will still cure a lot of ills. I share your hopes about NT 8 and .NET.
Basically, glad you got things going again.
Bob.
When one door closes, another opens.
-- Cervantes, Don Quixote
. All I've done in a while is programming, and now essentially trading...