I applied extremely aggressive optimization techniques that should reduce the CPU cycles on COBC false by 90% or more compared to the original version. I used every trick I could think of: moving code that was executing on every tick to OnStartUp(), using predefined instances of the external indicators, and redundant tick rejection. If you select EMA's, they will be calculated within the indicator, without any need to use an instance of the EMA class.
This is provided as a protected assembly. I don't have to give away all of my secrets, do I? 
Why do this? Optimally coded indicators load faster, and use less computer resources while running. CPU cycles are not free. Using less of them makes Ninjatrader more responsive and reliable. Charts load faster, and lag less in fast markets. Crashes and freezes become less frequent.
Have you noticed how quickly this indicator loads, and how responsive it is? Please leave comments regarding your experience with this version. Maybe some day ALL of your indicators can be coded like this.....
Category The Elite Circle
|
|
|
View Download Details
