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 afraid I have to agree that rapidly clicking in sim mode (where all ninja needs to do is increment or decrement a counter) really only demonstrates how ninja trader handles rapid clicks in sim mode. Still it is always good to have people try to break stuff. Clicking is not really a problem for any platform, how things behave in fast markets where they need to handle hundreds and hundred of order book changes every second is what will likely cause hiccups if anything will. Stuff like that is pretty hard to test though you can run a Ninja DOM alongside TT for example. (Incidentally I know which I would use given a choice)
Really when talking about NT one needs to differentiate between the order entry and the charts. The order entry has always been adequate especially if you are not a scalper. I remember being one of the few people that tested the first version an eternity ago. The charts while having some nice features are poorly architected (and still are in 7.0). It was also clear in 6.5 there where issues with how NT was using .net (it's always a tricky task getting the best performance out of a managed framework). Actually the rapid clicking will exercise .net'/NT's UI event handling.
Having said that I quite like NT it is different enough to be interesting and is fine for basic charting and order entry. I hope one day they sort out the database and tick precision for historic data so stuff like gomi's database are not required, and more advanced applications can be developed without too much fuss. Of course they need to keep streamlining and optimising the data handling too as even in version 7.0 there is room for improvement.
@Big Mike and I had a discussion about real vs. SIM, months ago.
The idea is we set a trader in front of a trading system and it randomly sets real vs. sim for each completed trade. Then you trade for a fixed amount of time.
At the end see what the results are. We should do this!
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
I think the part that has been lost is my point that rapid clicking pales into insignificance compared to rapid incoming ticks in fast markets, unless of course you where clicking 1000's of orders a second. It is all about handling events and incoming ticks in fast markets are where you get a truckload of events. If you want to stress more subsystems have lots of single tick charts with a reasonable history updating too.
You are not beta testing anything that is linked to the real world, like I said the bottleneck is the API and in your SIM101 you're not using it to the max like in live trading. Beta testing in the normal software world is in a lab, with a simulated environment. Meaning you use an API, even in your 'non' real account.
Apparently ninjatrader has no clue about how software testing and stress testing works otherwise ninjatrader wouldn't be such a piece of crap like it is today.
Ninjatrader was hot in 2008/2009, they blew it, their momentum is over and now others will jump in and that their market over. That's how things go when you mess up, and boy, you really messed up NT !!
