Memory Issue with OHL?

[alabell]

Looking at the code of the indicator shows that on each BarUpdate, it is running 3 for loops over the entire length of the chart.

That means NT has to iterate through the domain to find the correct instance of the indicator, then run 3 for loops. If you are using COBC = false, then it must do this for every tick. (Remember the magic wrapper code that NT places at the bottom of the indicators, and warns you not to even glance at?) A nasty "fine how do you do" right there.

One way to reduce the load, especially if using COBC = false, is to use a named instance of the indicator class. That way, NT knows exactly which code location to call, without having to go look for it.

Forgive my ignorance in this case, koganam, but can you explain the concept behind the 3 for loops, and in addition, how you have determined this about the code?

BTW, COBC will be set to true for this strategy, it is not in indicator format, if that makes a difference.

Thanks in advance for any help,


Andrew

[koganam]

Forgive my ignorance in this case, koganam, but can you explain the concept behind the 3 for loops, and in addition, how you have determined this about the code?

BTW, COBC will be set to true for this strategy, it is not in indicator format, if that makes a difference.

Thanks in advance for any help,


Andrew

Just look at the code in the editor, and you will see that there are 3 for loops that loop over the barSeries.Count.