Issue #1 NinjaTrader Unresponsive
Most of you already know that the flexibility NinjaTrader provides in the context of programming scripts is unsurpassed but this comes at a price. The majority of performance related issues are attributed to custom scripts that eat CPU cycles. This is outside the control of NinjaTrader application itself. Any individual could unknowingly write one bad line of code that can bring NinjaTrader to its knees. If you are running custom scripts, I would take a look there first. In addition, I suggest reviewing the following section from our Help Guide on ways to optimize performance. If you are unable to make progress, let me know and I will offer further help. I can assure that this issue is not related for the Zen-Fire data feed.
Issue #2 Historical Data Gap
I too was suspicious that maybe there was a performance issue that brought the server down however, after further analysis this was not the case. I am deadly serious that the gap will be filled on the weekend during server maintenance. Is this optimal, of course not but it’s the reality. In general, server stability has not been an issue and today’s event was an exception to the norm. We will take steps to understand what happened and determine how we can minimize customer impact should this happen in the future.
The following 2 users say Thank You to NinjaTrader for this post:
On a constructive level, what happened after the platform froze was defined by NT customer service and related to historical data issues. Apparently for those who didn't crash the system it was ok and honestly it was a bad coincidence. Did you find out why the the platform crashed (I would follow the suggestions of fluxsmith), I challenge you to find a platform that has zero problems, or if you want you find it out by your own and report back to this thread eventually.
Thank you all for your comments supporting me. They mean a lot. It's unfortunate that some conversations have to turn out like this. It's also unfortunate that people can make things up to say about someone or a product without presenting any facts to back up their claims. Once again, futures.io (formerly BMT) is proven to be a great place to live and work.
By the way, I'm not an employee of NT nor associated with them in any way except to be a long time user of their product, since version 6.
The following 2 users say Thank You to MWinfrey for this post:
There is some bad news however, this guy might be right it happened again at just after 5 PM Eastern time on 6J, this was when the market took a big dip as stops got triggered when the $/Yen passed its 1995 low. Looks like the high volume trade data is causing a problem, unless of course there was another strange outage like earlier in the day. 2 times in one day, I am getting suspicious.
There was not a data server outage around 5 PM ET yesterday. If you are referring to being disconnected from a server, that is a different issue and could be attributed to many things includind internet line quality at that time.
The following user says Thank You to NinjaTrader for this post:
Everyone has different equipment with varying degrees of processing power. I run around 20 charts (many using Range bars) and at least eight instruments and never experienced so much as a blip at that time. I know everyone here has had bad experiences at one time or other but these are not usually platform wide. To have someone come in and trash talk the whole platform because he had a bad day kind of irks me a little. Every platform I ever used has had problems but most problems were specific to my setup, such as having 60-70 charts open during FOMC and experiencing locked up charts for example. I always look to the NT forums for other users having the same problem as me and to assess whether it is isolated or is a new bug that needs to be squashed. Fortunately, bugs are usually taken care of in the next release.
The following 5 users say Thank You to eDanny for this post:
Our business has been growing fast and we already had plans to expand our server farm capacity to meet demand however, yesterday’s exception occurred prior to our ability to do this. We do have redundancy in place however, at the time of the crash, the amount of users we would have had to redirect to another server was not possible without introducing serious risk to stability. That being said, we have accelerated our plan for capacity expansion and hope to have it online soon in order to minimize end user impact in the rare case of an exception in the future.
In the interim, if there are any NinjaTrader 6.5.1000.14 or earlier users (a few hundred only) on Zen-Fire, I advise you to upgrade immediately to the current NinjaTrader 6.5.1000.19 or NinjaTrader 7.0.1000.4. In the foreseeable future, historical data access will be disabled for these outdated versions of NinjaTrader.
The following 3 users say Thank You to NinjaTrader for this post:
I think there was a pb with data yesterday (16/03).
I have 8 chart, 7 Mn and one in Range.
On my charts Mn, I had a Gap from 16:00 for a period of 40 Mn.
But curiously, the single chart in Range, I had no Gap.
In, Historical DataManager, in the section of Mn, Dats missing.
But in the section Ticks, they were present.
I downlode the Data Mn, but the Gap was still present.
So I exported my Data in Ticks and regenerate Mn Data for the charts correctly.
This may perhaps help you better understand the pb.