How to free indicator resources? indicator called from EA

With http://docs.mql4.com/indicators/icustom I am calling an indicator.
It becomes slow, but not that the problem.

At EA there is a tick and every time it calls it and becomes unresponsive and can't finish a test ( not an optimisation )
I am wondering how should I implement something to free the resources from the indicator?

My indicator use auxiliary buffers for signal filtering and it has like this:

I suspect at least those 4 aren't deleted.

Any help?

from my personal experience one thing, that is extremely slowing down iCustom, is passing of parameters
the more input parameters your indicator has, the slower iCustom will be
to work around this, best would be to call iCustom without any parameter and use the default settings of the indicator

Hi,

I have not come across a mechanism to free up resources from an indicator once you have included included/called it in an EA (or another indicator) through iCustom().

I have also no experience comparable with iwjw's experience - but interesting!!!

A number of things might help in resolving your issue:

1. check in detail what happens in your indicators and then in your EA, and check how long different parts of your calculations take: You can use t0=GetTickCount()...do loop/calculations....t1=GetTickCount() and then print out with some additional info to allow analysis

2. do you really need to calculate your indicator with every tick? Does your strategy require knowledge of everything your indicator calculates on every tick, or could you just access the information from your indicator at the start of a new bar and then allow trade entry at the start of the new bar if conditions are correct. If the latter is true...you can simply stick access to your indi in a construction such as: if(NEWBAR) { ....access icustom(indi) .... do your thing based on calcs }

3. if access to the indi is required every tick, and if iwjw's solution also does not help because you need / want to vary these parameters, you may be able to transfer the logic and calculations from your indicator to your EA. The main difference between indicator and EA code (for your question) is that in an EA you have no access to buffers. Dependent on the structure of the code in the indicator, and on how the information from buffers on previous bars/calls influences the value of the buffers on the current bar, you could consider an implementation of your indicator without buffers.

If you can call your indicator on NEWBAR, you could store the previous value(s) of relevant variables in a short array, or even individual variables before you calculate the values for your current bar. The downside is that you need to do some manipulation of data yourself (and need to figure that out - and consider unexpected consequences), but the upside is enormous, because it avoids calling iCustom(indicator).

Hope that some of that helps.

But: if your terminal freezes because of calling the iCustom(indicator) there may well be something else wrong in your indicator. Unless your indicator does a ricidulous amount of calculations. I have implemented variety of EAs with access to very complex of time consuming indicators. In such cases the terminal has slowed down, and in such cases the terminal prints out statements in the log file along the lines of 'rewrite your indicator as it takes too long to calculate'. The getting into the meat & detail of the indicator tends to resolve the issue.

Cheerio,
John

Somebody gave me a tipp as not the indi's fault, but the EA, because I am checking my existing orders and so on.
I have removed almost everyything from EA and let just a 2 call.


This part of the code is EXPONENTIALLY SLOWING DOWN.


I would like to trade exactly what the Indi shows.
If I grab all logic from Indi to EA, then it will not be exponentially slow, just slow, as how I am using it at MT4.

BTW: that indi has:
and code calls to do his stuff.
Whem is in regular chart view I see it is a clear problem with him and performing very-very slow at timeframechnages ( load and unload ) and cliching different timeframes doesn't help: it becomes slower, but it can be 6-7 times only.

There is the problem: http://www.forexfactory.com/showthre...55#post7802255


has a leak,

MT4.0 Build 840, 12 Jun2015 - the latest at my broker

Metaquotes comfirmed the bug and they response


1. You should open demo account on MetaQuotes-Demo server and log in.
Accounts -> Open an Account -> click "add new broker ..." -> enter demo.metaquotes.net -> click "Scan" -> select demo.metaquotes.net -> click "Next".
2. Restart the terminal.
3. Wait until "LiveUpdate finished" record would appear in Journal tab.
4. Restart the terminal once again.
5. Check terminal's build."

Cheers...not very nice...at all....but at least it's been resolved?

Cheerio,
John

I need " Candles Ratio " mt5 indicator which is designed to identify specific types of price action based on the relative size of the candlestick body compared to the body of the previous candlestick and on the relative size of the wicks (or shadows) compared to the body of the candlestick.

Formula
Candle Body % = (Candle Body Length / Previous Candle Body Length) *100
Candle Opening Wick % = (Candle Opening Wick Length / Candle Body Length) *100
Candle Closing Wick % = (Candle Closing Wick Length / Candle Body Length) *100

In mt5 Indicator " Candles Ratio " parameters window I can choose what type of candles should be finding:

Inputs
Candle Body % = 200
Candle Opening Wick % = 20
Candle Closing Wick % = 30