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)
The coding of the Ninjatrader stochastic is pathetically inefficient, horrible, a joke. So it is not a good foundation for anything.
Calling the MIN and MAX functions on every tick is extremely resource intensive. unnecessary, and serves no useful purpose.
Since MIN and MAX are external classes, durable predefined instances of them should be created once and reused. Or, better still, the MIN and MAX routines should be placed inside the stochastic.
There is a thread on futures.io (formerly BMT) about Optimizing C# code. I wish somebody would read it. One of the posts on that thread is a superfast version of the DOUBLE stochastic. It illustrates the techniques that should be used in THIS indicator.
Maybe I will post an alternate version of this indicator to show how much better it can be made to work.
This type of coding is the cause of the vast majority of Ninjatrader performance problems. Throwing more cores at it, or switching to inferior platforms in disgust, are not the best solutions.