This may be a difficult one but I'll run it past you anyway.
I've coded up a trailing stop strategy that would ideally be calculated with each tick rather than on the close of each range bar.
(This strategy is a bit more intricate than with the usual auto trails. which are, I believe, calculated with each tick but which are not, I would guess, very CPU intensive.)
My worry is how CPU intensive strategies can be with CalculateOnBarClose = False. I haven't got a very powerful PC: dual core 1.8 with 2GB RAM.
Is there any way of estimating how CPU intensive a strategy is? I'm worried that my slightly antiquated CPU may go into meltdown!
It may be imperative for me to upgrade my PC system, of course.
Any pointers you could give me would be much appreciated.


Comment