Unfeasible performance and frequent overloads in Automate tab of version 3

lavio@gigalink.com.br
20 Aug 2018, 04:57 ( Updated at: 21 Dec 2023, 09:20 )

A very usual overload

A very usual situation when I try to open CTrader is in the following screen capture. This one was taken after returning from hybernation. But it happens sometimes if I just minimize it for a coupple of hours.
"não respondendo" means "not responding".

lavio@gigalink.com.br
20 Aug 2018, 04:58

RE: A very usual overload

lavio@gigalink.com.br said:

A very usual situation when I try to open CTrader is in the following screen capture. This one was taken after returning from hybernation. But it happens sometimes if I just minimize it for a coupple of hours.
"não respondendo" means "not responding".

It takes about 5 minutes to return from this state.

Yes, sorry if I am upset. But I am getting tired of so many difficulties to work with this version 3 of CTrader.

Lavio

lavio@gigalink.com.br
21 Aug 2018, 14:54 ( Updated at: 21 Dec 2023, 09:20 )

More "not responding" situations on everyday usage

Here it is, one more time, it is stuck after night. What did happen? A temporary disconnection and it crashes "reconnecting". This is how version 3 is working.
Where are spotware guys that say nothing about this crazy version 3 of CTrader?

PanagiotisCharalampous
22 Aug 2018, 09:50

Hi Lavio,

Posting the same issue over and over again doesn't really help us. If you want to help us please send us the following

1. The cBot you are using.
2. The instances you are running.
3. The parameters for each instance.

This way we will be able to setup the same environment on an internal pc, reproduce the issue and understand the cause of it. You can send me the information at community@spotware.com.

Best Regards,

Panagiotis

lavio@gigalink.com.br
24 Aug 2018, 05:25

RE:

Panagiotis Charalampous said:

Hi Lavio,

Posting the same issue over and over again doesn't really help us. If you want to help us please send us the following

1. The cBot you are using.
2. The instances you are running.
3. The parameters for each instance.

This way we will be able to setup the same environment on an internal pc, reproduce the issue and understand the cause of it. You can send me the information at community@spotware.com.

Best Regards,

Panagiotis

 

I have already explained in previous messages and AS YOU CAN SEE in the pictures above there are 9 charts with more than 30 cbots running.

So, it is not possible to say to you "the cbot you are using".

The problem is not because of the specific cbots. As I also said previously, in version 2 there was not such serious overload issues. They started with the "integration".

-----> If you want to reproduce the same problems, just add more than 30 cbots running in the Trader tab and then try to work on the Automate tab to see what happens!

And NO, the cbots I use DO NOT overload the application using a lot the OnTick() event, one tick at a time. When ticks are necessary, I use a reducing factor to avoid running every single tick the same code (it would be useless and not efficient). Also, the OnTimer()  event is not used when backtesting.

In normal situation, the cpu load is less than 10% with all cbots running.

Again, I need to remember you that I had to stop using ticks, to use only the M1 simulation, in the Automate tab, because of performance issues in optimizations. In version 2, using the independant CALGO, this never was necessary. The simplest solution is obvious, even if you do not want to admit it.

Thanks

Lavio

lavio@gigalink.com.br
24 Aug 2018, 15:26

RE:

Panagiotis Charalampous said:

Hi Lavio,

Posting the same issue over and over again doesn't really help us. If you want to help us please send us the following

1. The cBot you are using.
2. The instances you are running.
3. The parameters for each instance.

This way we will be able to setup the same environment on an internal pc, reproduce the issue and understand the cause of it. You can send me the information at community@spotware.com.

Best Regards,

Panagiotis

 

Complementing.... I wrote above that in all cbots I use the OnTimer() event is not used when backtesting. And when running it only writes some text in the chart every 10 SECONDS. So, it does NOT overload the application.

Another important thing I would like to tell.... notice that now, after the "integration", I WAS FORCED to use a second computer to run a second instance (*) of CTrader IC Markets to be able to use the Automate tab optimizing and backtesting. In the computer where I run the cbots in the Trade tab, it is impossible. It overloads, gets stuck, crashes, pops back screens, "not responding" status for minutes etc etc etc. NONE of these problems I had whyen using the independant CALGO.
And yes, I need to repeat this over and over, because it seems spotware is ignoring a very important performance issue here created with the "integration".
And I will repeat again: let the version integrated as it is, BUT ALSO add an independant Calgo application for those who use the "automate" a lot. Do this, and most overload problems will be solved.

(*) this because if I run in the same computer a second instance of CTrader app, it can lose all cbots I am running in the charts if I forget to close the main the application last ! Why don't you save al cbots as well in the workspace?







 

lavio@gigalink.com.br
24 Aug 2018, 15:26

RE:

Panagiotis Charalampous said:

Hi Lavio,

Posting the same issue over and over again doesn't really help us. If you want to help us please send us the following

1. The cBot you are using.
2. The instances you are running.
3. The parameters for each instance.

This way we will be able to setup the same environment on an internal pc, reproduce the issue and understand the cause of it. You can send me the information at community@spotware.com.

Best Regards,

Panagiotis

 

Complementing.... I wrote above that in all cbots I use the OnTimer() event is not used when backtesting. And when running it only writes some text in the chart every 10 SECONDS. So, it does NOT overload the application.

Another important thing I would like to tell.... notice that now, after the "integration", I WAS FORCED to use a second computer to run a second instance (*) of CTrader IC Markets to be able to use the Automate tab optimizing and backtesting. In the computer where I run the cbots in the Trade tab, it is impossible. It overloads, gets stuck, crashes, pops back screens, "not responding" status for minutes etc etc etc. NONE of these problems I had whyen using the independant CALGO.
And yes, I need to repeat this over and over, because it seems spotware is ignoring a very important performance issue here created with the "integration".
And I will repeat again: let the version integrated as it is, BUT ALSO add an independant Calgo application for those who use the "automate" a lot. Do this, and most overload problems will be solved.

(*) this because if I run in the same computer a second instance of CTrader app, it can lose all cbots I am running in the charts if I forget to close the main the application last ! Why don't you save al cbots as well in the workspace?







 

PanagiotisCharalampous
24 Aug 2018, 15:58

Hi Lavio,
You keep writing the same things over and over again. I will summarize below my replies to all subjects and leave the discussion here

1. You insist in using only one instance of cTrader while we have advised you to use separate instances of cTrader Trade and cTrader Automate as so many other traders do without a problem.
2. Indeed there is an issue when running two instances that might result in overriding your workspace and cBot settings but 
   1. We reproduced and acknowledged the issue and we are going to fix it. 
   2. There is a workaround which you can use until it is fixed. Just close the cTrader Trade instance last and there will be no issue. You can also try using different workspaces for each instance.
3. You correlate the memory problem you face with the fact that we merged cTrader and cAlgo while there is no evidence neither any technical explanation how these two facts should be be related. We asked for the cBot and information on your setup in order to reproduce and fix the problem but you ignore our request insisting in your proposal to have the two applications separated, believing that this is the solution to the problem. I did not blame your cBot anywhere for the memory issue. We just need it to reproduce the issue and fix it.

Concluding, it would be much more productive to help us fix the current issues instead of writing all the time your suggestion to go back to cTrader and cAlgo, something that will probably not happen.

Best Regards,
Panagiotis 

sifneos4fx
25 Aug 2018, 11:16

Hey Lavio, 

I am pretty sure, you need more RAM, if you got 8GB that wouldn be not enough for such operations. If you want to increase responsivness while optimizing, you will need at least 12GB, best 16-20GB. But even then, do not expect miracles in performance, as optimizing is a very heavy operation. While running optimization, all other tasks will slow down, there is one solution to this, buy serious hardware, i.e. check the Dell PowerEdge solutions.

lavio@gigalink.com.br
25 Aug 2018, 15:14

RE:

patrick.sifneos@gmail.com said:

Hey Lavio, 

I am pretty sure, you need more RAM, if you got 8GB that wouldn be not enough for such operations. If you want to increase responsivness while optimizing, you will need at least 12GB, best 16-20GB. But even then, do not expect miracles in performance, as optimizing is a very heavy operation. While running optimization, all other tasks will slow down, there is one solution to this, buy serious hardware, i.e. check the Dell PowerEdge solutions.

Hi Patrick, thank you for your advice.

I use Core I7 based machines, 12 GB DDR3 Ram, SSD drive and W10.

My main point in this thread is that when using version 2, with Calgo independant, I had no such serious performance problems and was used to do everything using ticks, not the M1 simulation. They started with the "integrated" version.
As I wrote above, now I use the M1 simulation and also need two instances of CTrader, one to run the trades, other to run the Automate, like I used Calgo and CTrader before. But because of a bug in saving cbots, I cannot do it in the same computer without the risk to lose the many cbots settings running. Mr. Panagiotis admited the problem in the previous message and said it will be fixed. Let's see.

Yes, of course, I am aware optimizations are heavy. But this is not the problem. Small overloads happen even wiht simple things like to open a chart. I have used Ninja, a bit of Metatrader and CTrade for YEARS and I know what I see, I am not naive on using and programming computers. To me is quite obvious that to integrate the Automate and the Trade in the same application was not a good idea and I am really impressed they do not admit it. But they are the boss and I am thinking on Metatrader if things do not get better in short time.

Thanks, Lavio