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 have attached 2 indicators that are not very different in what they do.
also its nearly the same plots + code-lines.
but their loading-time very very differently when ading them in a chart.
my question is : Why is this VolatilityStop- indicator loading so slowly with high CPU-usage ?
i cant find the reason in the code by myself - but i would love to find it out
any ideas ?
also a question : will this "loading so slowly" eat more recources in realtime-action than a fast loading one when i use the indicator in a strategy ?
or do you think its only the first initial loading that takes so much time + cpupower ?
special Qs for special guys i think
looking forward to intersting ideas !
VolatilityStop = slow loading ATR-Trailer = fast loading
BTW - thats all NT6,5 stuff.
.
max-td
Can you help answer these questions from other members on NexusFi?
If this answer did not help you, you need to check the code in lines 81 and 102 of the volatilitystop indicator. "counter" may take a higher value than "period" as used by ATRTrailing. The MAX and MIN methods are the public servants of the NinjaTrader methods, they are executing the job you ask, but slowly.
i changed counter in this - SignalClose = MIN (Close, (counter)) [0] ; and in the visaversa-line --
into a static variable for testing and it loads fast as hell
for shure it plots an other line too - but that wasnt the question now.
ok - thanks a bunch for the input!
so my second question was if this indicator makes also a strategy permanently more heavy than a fast loading one while running realtime ?
or does this only affect the loading-process ?
I think the main point is that counter can take much larger values than period. I do not think that the access of a dynamically defined variable is slower than the access of a static variable. You could try to substitute counter with a large fixed number and see what happens.
i dont have to find out the deeper why now ... but this i like to get answered if possible :
so my second question was if this indicator makes also a strategy permanently more heavy than a fast loading one while running realtime ?
or does this only affect the loading-process ?
