Replies

dejonge4
12 Nov 2024, 21:57 ( Updated at: 13 Nov 2024, 06:22 )

RE: RE: RE: RE: Memory Manager bot

dejonge4 said: 

PanagiotisCharalampous said: 

dejonge4 said: 

PanagiotisCharalampous said: 

Hi there,

Could you please send us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.

Best regards,

Panagiotis
 

Hopefully you received the text as per the above instructions. The happens every time I try to Optimize a trading bot. The first pic is my % of free RAM before Optimization begins and the second pic is after 4 minutes of Optimization.

Image preview

Thank you. Unfortunately troubleshooting does not provide any useful information. It it possible to run dotMemory and provide us with a memory snapshot?

Geez, not at those prices. I would most likely never use dotMemory apart from trying to resolve this. The following pic clearly shows the issue is with cTrader. The last algo shows high memory use when optimizing. All other algo's listed will do the same if I re-optimize them. I had the same issue with the previous version of cTrader so I bought the Memory Manager bot which worked until the update.

I may have resolved this. I downloaded a simple sample bot, ran optimization and found the RAM usage stabilized as there were a lot less logs. My bots have many parameters with each having a broad range of values.  The new cTrader version has had an impact on my trading bots but it might be that I need to trim them up to be more efficient. I will work through my bots and clean up the codes including reducing high numbers of print logs. 


@dejonge4

dejonge4
12 Nov 2024, 20:57 ( Updated at: 13 Nov 2024, 06:22 )

RE: RE: RE: Memory Manager bot

PanagiotisCharalampous said: 

dejonge4 said: 

PanagiotisCharalampous said: 

Hi there,

Could you please send us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.

Best regards,

Panagiotis
 

Hopefully you received the text as per the above instructions. The happens every time I try to Optimize a trading bot. The first pic is my % of free RAM before Optimization begins and the second pic is after 4 minutes of Optimization.

Image preview

Thank you. Unfortunately troubleshooting does not provide any useful information. It it possible to run dotMemory and provide us with a memory snapshot?

Geez, not at those prices. I would most likely never use dotMemory apart from trying to resolve this. The following pic clearly shows the issue is with cTrader. The last algo shows high memory use when optimizing. All other algo's listed will do the same if I re-optimize them. I had the same issue with the previous version of cTrader so I bought the Memory Manager bot which worked until the update.


@dejonge4

dejonge4
12 Nov 2024, 10:22 ( Updated at: 12 Nov 2024, 11:13 )

RE: Memory Manager bot

PanagiotisCharalampous said: 

Hi there,

Could you please send us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.

Best regards,

Panagiotis
 

Hopefully you received the text as per the above instructions. The happens every time I try to Optimize a trading bot. The first pic is my % of free RAM before Optimization begins and the second pic is after 4 minutes of Optimization.

Image preview

@dejonge4

dejonge4
10 Nov 2024, 13:54 ( Updated at: 10 Nov 2024, 15:35 )

RE: New update made my algo stop working- backtest not working either

nayibseluja said: 

As I stated in the subject. The new update is not working. Backtest is not getting any trade, and it's not actually loading in some instances. I already deleted and reinstalled and same issues. Can I roll it back? Or can you guys fix this please?

Also memory manager bot no longer working. Cannot back test anything without the RAM being totally used up. Have deleted the memory manager bot and reinstalled, compiled and it runs but it does nothing to manager RAM use. 

 


@dejonge4