How to avoid, mt5 generating bar*.tmp files

[kekkis]

If using agents or multiple cores for optimizing parameters, more than one year.
Mt5 generates \tester\Agent*\temp\bar*.tmp files. every run.

It slowly gnaw/nibble SSD storage. in mt4 read only fxt files was solution. How about mt5.

if using multiple cores and optimizing many symbols, will end up manufacturers TBW values quite soon, if not have TBW +600.
its like a wood worm problem for sailing ships.

Any Ideas ?

[kekkis]

for single symbol i should have enough ram, 32gb.
I dont understand why MT5 dont share tickdata with different cores.

[tickstory]

Hi Kekkis,

Is there any further discussion about this on the MQL forums? Do you know what the tmp files are for and if Metaquotes are proposing a solution?

Thanks.

[kekkis]

I have'nt seen any discussion in mql5 forum, or forexfactory.

Those agent folders where mt5 is genrating files, the folder size are all same for every agent/threads and they are many GB's each.
and they are deleted. I havent done file comparassion but, what else mt5 generates than bar/tick data, same way how the mt4 creates fxt files.

[tickstory]

Hi Kekkis,

It sounds like something that would need to be raised with Metaquotes. If this is required by the tester for its operations, there is no way around it except a MT5 code change.

I imagine the only short-term solution would be to install MT5 on a removable drive that has sufficient disk space.

Regards.

[kekkis]

I posted wrong topic area, question in mql5 forum, i try to ask if they service desk can read it.
16 threads, mt5 is writing +35GB,five years for one symbol.
many consumer ssd's which tbw value is under 300 tbw, this will be be issue or just a waste of resources/money.
It should'nt be a problem use shared directory or memory for local agents/threads if need to generate those files while using strategy tester.
or keep those files alive , and not delete after session/closing mt5.