Help wanted: recently installed Build 225 hogs cpu...
thanks for time taken to show your usage stats.
on perhaps a similar vein, just what is the preferred method to inhibit EA body execution? this has been aired many times but do not think came to a single 'best practice' method resolution...
div/0? or internal flag+immediate exit on .t.?
or?
asking as due to a logic error, an EA return(ERR_COMMON_ERROR); on each tick with a log msg = 4hr+ of cpu at 100% and vLarge log.
seems like an EA returning common error code should be enough to inhibit further invocations, seems not. you have method?
phy, like your cray :)
Yes, built PC for the "next five years" ... One year is up already...
How to stop an EA, "best" method? Best is a qualitative judgement, best is what you like.
Maybe use GlobalVariableSet/Get - all your EA can easily access the data, and it can be set manually too.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Build 224 did not exhibit consistent 'need' for over 90% on regular basis.
running on terminal:
12 symbols in market watch
2 simple charts - no heavy indicators...
using Process Explorer from sysinternals.com the graph is consistently spiking and holding for seconds at a time in the 90% + range.
as said, Build 224 was never like this new build.
IF have any suggestions THEN please tell all
Thanks