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'm on NT8 for 3 months now and have not experienced any issues. Having said that, I'm not doing anything out-of-the-ordinary.
I did experience a couple of coding issues when converting my indicators but worked around it. I'm not experiencing issues during market replay.
Of all NT changes, I really like the tabs in NT8.
Trading: The one I'm creating in the present....Index Futures mini/micro, ZF
Posts: 2,311 since Nov 2011
Thanks Given: 7,341
Thanks Received: 4,518
Sounds good thank you.
Just for some different info....
I have asked for, and been told by Trading Computers, who I buy all my machines from, that speed is the number one requirement of trading machines and a multi processor machine would be slower but great for a server type application.
Are you recreating your workspaces on a regular schedule? I find many problem arise once a workspace starts to age as well as weeding out possible corrupt data.
Have you worked with @NinjaTrader on your issues? I find it best to present them with videos documenting the problem. Many of them!.....lol
Ron
...My calamity is My providence, outwardly it is fire and vengeance, but inwardly it is light and mercy...
The steed of this Valley is pain; and if there be no pain this journey will never end.
Buy Low And Sell High (read left to right or right to left....lol)
The Xeon machine I built for backtesting has 8 cores each processor for 16 total and 32 threads. I built it specifically to take advantage of NT8 backtesting engine and use of multiple cores. Should be a beast of a number cruncher once NT8 starts working correctly. These processor are normally $1000 each but I was able to snag for $100 each and build a machine around them. Facebook and others have dumped a lot of the 2670 processors on the market all at once because more power efficient ones out.
I have looked at workspace issue but it is not the problem.
Yes in extensive contact with NT support.
"The day I became a winning trader was the day it became boring. Daily losses no longer bother me and daily wins no longer excited me. Took years of pain and busting a few accounts before finally got my mind right. I survived the darkness within and now just chillax and let my black box do the work."
In my experience NT8 is still not ready for prime time, a glance at the release notes is enough to see why, a raft of bugs fixed in each and a further raft outstanding, a dozen or more of which are mine. I dare say serious users/providers are well into far bigger lists. A stable platform needs an asymptotic decrease in buglist content, although at least the situation is relatively transparent.
I've now ported a truckload of 'ordinary' NT7 code to NT8 in less time than I expected, but found far more problems than I expected, surprisingly even basic datafeed issues, or even simple Print statements that crash it if more than one output window is open. I have not tried to go outside supported areas, settling for minor or safe Forms v WPF changes only where necessary. Fortunately, most supported graphical/computational code ports well and straightforwardly, with just a building 'gotchas' list to avoid. However, serious development for the new beast does require a greatly increased level of diligence and awareness of multi-processing issues, take heed and always wear a code condom.
All that said, it is definitely usable in a 'getting to know you' kind of way. I'm glad I made the start and do continue to run it intermittently in parallel on different machines to see how the releases are evolving. Interestingly, all the bugs I've found reproduce equally well on a wild variety of graphics cards and processor or motherboard graphics combinations, although I'm also sure WPF itself is not helping stability. Sadly NT8 will still crash all on its own without any user code involved and not always in reproducible ways, sometimes with database or xml faults.
I haven't experienced the memory leak issues that others seem to have encountered, but find some of the numbers reported to be staggering. If true, then all performance benefit from extra cores utilisation will be swamped anyway. Hopefully, as understanding and coding practice improve along with release reliability, this should become less of a problem. My dark concern is that fundamental design reliability has been compromised by an over-ambitious and over-hyped launch. Let's hope not.
I'm assuming support and development are severely overloaded and hope the situation improves greatly over the coming year. I still regard it as early days and remain committed, pending outstanding bug-fixes and quality jumps, but for now will remain an interested and happy non-user.
I appreciate all your comments and thoughts on this thread.
For sure NinjaTrader 8 is in its early days and you can expect longer than normal fix lists from release to release especially when contrasted to a mature product like NinjaTrader 7 which is in its 8th production year.
That being said, a few comments from my perspective.
As others, have said, development of custom scripts in NinjaTrader 8 is a lot more flexible and powerful however, one needs an increased level of diligence (I like the code condom reference ) as memory leaks can easily sneak in. Most memory issues that come across our help desk have been related to custom indicators.
That’s not to say we are not guilty With the help of our developer community, we were able to isolate a chart rendering thread lock issue that we believe can result in a memory leak. This can affect a subset of a subset of users who consume custom indicators that override the OnRender() method. This fix will be in R6 due out next month.
To put usage in perspective, as of last week, we are averaging nearly 3,000 daily users and growing
In any case, its with your feedback that we are able to make NinjaTrader a great product so thank you for that.
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.
sienna, you can help us by posting a picture too of what you are referring to. Are you referring to Market Replay (historical playback) or Tick replay (fine-grained bid/ask data)? If you are referring to Market Replay you are wise to download several days and then playback in the middle somewhere if you are having problems. If you are referring to tick replay (which is not really a replay) then when connected to your broker, right click on your chart "Reload Historical data".
SIM22,
Am referring to Market Replay Minute data (historical playback). My trading partner downloaded a few months data (minute) and tested at different speeds, across personal PC and a trusted VPS. We both use the same AutoTrade program from a vendor. On NT7 it worked without a hassle. On NT8 it gives different results and it cuts out at random, not placing any orders after a few days.
The vendor (who is not a snakeoil salesman) had his programmers test and test, concluding that it was the NT8 based Market Replay data. (It is fine on NT7). The NT8 tests were done a t 1X 200X 500X speeds....the reults were wildly different, combined with the randomn pauses in order placement, no matter the speed.
Now the first reaction is to question the vendor's AutoTrade program. However, when running on demo live (forward testing) the issues completely disssappear, as regards: randomn cuts outs and not placing any orders after a few days. Strategy Analyser also works fine (but I don't trust the results on SA). However, I am unable to test NT8 Market Replay (min) and there is the rub.
Short add on to my above post (kind of answers my own question). The vendor, whose autostrade program I use just came back with this: "......there are discrepancies with NT's Market Replay & Strategy Analyser on their end. They're attempting to remedy the bugs, however, have no firm date yet for resolution".
The main problem that I noticed is that when I was developing a multi-timeframe indocator, and was debugging using Visual Studio, after a few sessions of attaching/detaching to the Ninjatrader process, Ninjatrader would just crash without any error/warning/exception message.
Since developing my indicator, all has been great. I have monitored the memory and it seems stable. I was using Tradestation until the beginning of this month and it used to start running slowly even though I have the latest high spec machine.
Now since completing and running my new indicator, Ninjatrader is a pleasure to use and I wouldn't be able to do without the new features. The tabbed windows in themselves are awesome.
) as memory leaks can easily sneak in. Most memory issues that come across our help desk have been related to custom indicators.