Hitting memory limitations - page 2

New comment
 
Mike D-rock #:

That's actually pretty smart, thanks for the idea!

I'm surprised that longer backtest grows your memory significantly if you are only touching 3 symbols during your backtest. You might have a leak or something is constantly growing.

It depends of the testing mode, using "Real ticks" is quickly very heavy on memory.
 
Alain Verleyen #:
It depends of the testing mode, using "Real ticks" is quickly very heavy on memory.
Thanks for letting me know, I only used 1 minute OHLC and open price only modes for my purpose
 
Mike D-rock #:
Thanks for letting me know, I only used 1 minute OHLC and open price only modes for my purpose
Yes, me too, as real ticks optimization on multi-symbols is very unpractical if you want to test on several years.
 
Mike D-rock #:

That's actually pretty smart, thanks for the idea!

I'm surprised that longer backtest grows your memory significantly if you are only touching 3 symbols during your backtest. You might have a leak or something is constantly growing.

webrequest errors make it jump up and down, yeah. cant avoid those.
 
Michael Charles Schefe #:
webrequest errors make it jump up and down, yeah. cant avoid those.
You're doing webrequests during a backtest? Thought it was a prohibited call.
 
Mike D-rock #:
You're doing webrequests during a backtest? Thought it was a prohibited call.
seems that the calls still happen but automaticaly gives understandable error. but can have page of errors before the ea quits. its not my code btw. if it were, then i would not allow these calls during testing via code.
12
New comment