- #52
- Sep 25, 2017 10:27am Sep 25, 2017 10:27am
Like on Kim's declaration or war? "I LIKE THIS GUY" 
I had 15 charts, 3 of them with some decent set of indicators (no, not yours typical RSI and other empty. At the busiest time there was about 500 ticks per minute, so that is 10 ticks per second. Multiply that by 15 and that is 150 ticks per second and all that has to be updated o each tick. At least that is what the program will try to do.
I got about 50-60% CPU at i7 mobile. And probably about 30-40% on i7 quarto, but I run other stuff on that comp, for every tick as well
However at some point I had full set of charts open with full set of tools and at that time cpu usage was 100%, cTrader was not responsive, hard to switch tab ect. But I consider that normal. It was very busy time for the app. I cannot recall if it behave the same way a year or two ago, become batch of recent updates. Probably yes.
After couple minutes ticks came back to about 200 per minute and my i7 mobile is at 30-40%. i7 quarto at 25-30%.
Also I noticed RAM usage is rather high. At the moment cTrader used about 3Gb. I have 16Gb on that machine, but I guess swap will kick in somewhere near. That could be other reason for you, if you have less RAM (?)
I had 15 charts, 3 of them with some decent set of indicators (no, not yours typical RSI
and other empty. At the busiest time there was about 500 ticks per minute, so that is 10 ticks per second. Multiply that by 15 and that is 150 ticks per second and all that has to be updated o each tick. At least that is what the program will try to do.I got about 50-60% CPU at i7 mobile. And probably about 30-40% on i7 quarto, but I run other stuff on that comp, for every tick as well
However at some point I had full set of charts open with full set of tools and at that time cpu usage was 100%, cTrader was not responsive, hard to switch tab ect. But I consider that normal. It was very busy time for the app. I cannot recall if it behave the same way a year or two ago, become batch of recent updates. Probably yes.
After couple minutes ticks came back to about 200 per minute and my i7 mobile is at 30-40%. i7 quarto at 25-30%.
Also I noticed RAM usage is rather high. At the moment cTrader used about 3Gb. I have 16Gb on that machine, but I guess swap will kick in somewhere near. That could be other reason for you, if you have less RAM (?)
- #54
- Edited 11:11am Sep 25, 2017 11:00am | Edited 11:11am
- Joined Dec 2015 | Status: Trader | 7,803 Posts
Like on Kim's declaration or war? "I LIKE THIS GUY"
Like I said, it's not a PC problem. I have 2, sometimes 3 cTrader windows open with maybe 20-30 tabs. And one MT4 with some dashboard indicators.
cTrader uses maybe 5-10% cpu usually. Even when it is laggy and slow, it's not a hardware performance issue.
I run 32gig RAM, so no problem whatsoever with swap or running out of ram.
I did notice some time ago, that many drawing slow cTrader down aswell, so I stopped charting every little thing and keep it usually to pairs I might be interested in. Simple S/R lines and some fibo.
My custom indicators are mostly refreshed "on bar", not tick. I did that exactly for this reason, to minimize the load.
Btw, 95% of my tabs are H4 or D1.
The problem seems to be mostly when cTrader is kept minimized for some time. I can't open it and right-click close doesn't work either.
I have to kill the process and restart it. Then everything is fine again.
Never had this problem until recently.
I will try to observe this a little more, maybe I figure out where it comes from.
- #58
- Last Post: Sep 26, 2017 2:33am Sep 26, 2017 2:33am
JeremyV,
For curiosity I did some cTrader tests on my i7 laptop. Steps followed.
Step A) no cTrader open
CPU usage: 10%
RAM; 2.6Gb
Step B) 1x cTrader open with 15 almost naked charts,
30 minutes before London open:
CPU usage: 25%
RAM; 3.0Gb
Step C) 2x cTrader open with 15 almost naked charts,
30 minutes before London open:
CPU usage: 35%
RAM; 3.3Gb
Step D) 2x cTrader open with 15 almost naked charts,
Plus 1x cTrader with 15 heavy indi charts, 3
0 minutes before London open:
CPU usage: 50-60%
RAM: 5.2Gb
Step E) Leave the setup to run for a while and see what happens at London open:
Naked charts cTraders - easy switch between tabs. Heavy indi cTrader - switch between tabs lags about 0.5s, but still quite manageable.
No issue with bringing up minimized cTrader window, any of them.
cTrader with indis uses about 10x more memory then naked ones. The same with CPU at time of recalculating indis.
After 15 minutes RAM: 5.5Gb
Some time before London open, CPU usage went to 100% briefly and it took 1-2 second to bring back cTrader with indis to the front. Not a "freeze" though. Most of CPU usage was allocated to cTrade with indis, which is not surprising. naked cTrader are fully responsive.
Just before London open ticks are getting thicker. cTrader with indis become less responsive - to switch tab takes 1-2 second longer to do. Naked cTraders are still very responsive.
Right at London open cTrader with indis become quite unresponsive, CPU usage for that cTrader is 80-99% at times. Naked ones are still very fine. However tick volume for that time is 3-4x higher then before.
Step F) 2x cTrader open with 15 almost naked charts,
Plus 1x cTrader with 15 heavy indi charts,
10 minutes AFTER London open and all 3 apps running for 40 minutes:
CPU usage: 70-80%
RAM; 5.8Gb
In summary:
for me "freeze" happens with cTrader including a lot of indis. If at the same time many charts are open with many indies, it will cause temporary "freeze". Note: some of my indies are senitive on ticks, but for couple seconds at best. After coupe seconds I can open app, bring from the background ect, so the "freeze" is over. This is fully related to my custom indies and how I use them AND perhaps also how cTrader manages "cache" of them. The issue seems to be not exactly about recalculating an indi, but refreshing a window with data history. Naked cTrader works fine and is responsive all the time.
Additional the same setup with cTrader+indis on i7 mobile with 4 core taking 100% of CPU, resulted in 20-30% CPU usage on full i7 with 4 cores, which suggest hardware can be limitation.
So I would say, from my perspective, cTrader performance is on one side limited (obvious) by hardware and on the other side inefficiency of custom indies. cTrader by itself seems to be working fine. I cannot recall situation when cTrader would just freeze and I cannot open it any more and have to close it from the task manager, EXCEPT one that is loaded with a lot of custom indies. The more not optimized indies, the worse performance
Hope that helps with your debugging.
For curiosity I did some cTrader tests on my i7 laptop. Steps followed.
Step A) no cTrader open
CPU usage: 10%
RAM; 2.6Gb
Step B) 1x cTrader open with 15 almost naked charts,
30 minutes before London open:
CPU usage: 25%
RAM; 3.0Gb
Step C) 2x cTrader open with 15 almost naked charts,
30 minutes before London open:
CPU usage: 35%
RAM; 3.3Gb
Step D) 2x cTrader open with 15 almost naked charts,
Plus 1x cTrader with 15 heavy indi charts, 3
0 minutes before London open:
CPU usage: 50-60%
RAM: 5.2Gb
Step E) Leave the setup to run for a while and see what happens at London open:
Naked charts cTraders - easy switch between tabs. Heavy indi cTrader - switch between tabs lags about 0.5s, but still quite manageable.
No issue with bringing up minimized cTrader window, any of them.
cTrader with indis uses about 10x more memory then naked ones. The same with CPU at time of recalculating indis.
After 15 minutes RAM: 5.5Gb
Some time before London open, CPU usage went to 100% briefly and it took 1-2 second to bring back cTrader with indis to the front. Not a "freeze" though. Most of CPU usage was allocated to cTrade with indis, which is not surprising. naked cTrader are fully responsive.
Just before London open ticks are getting thicker. cTrader with indis become less responsive - to switch tab takes 1-2 second longer to do. Naked cTraders are still very responsive.
Right at London open cTrader with indis become quite unresponsive, CPU usage for that cTrader is 80-99% at times. Naked ones are still very fine. However tick volume for that time is 3-4x higher then before.
Step F) 2x cTrader open with 15 almost naked charts,
Plus 1x cTrader with 15 heavy indi charts,
10 minutes AFTER London open and all 3 apps running for 40 minutes:
CPU usage: 70-80%
RAM; 5.8Gb
In summary:
for me "freeze" happens with cTrader including a lot of indis. If at the same time many charts are open with many indies, it will cause temporary "freeze". Note: some of my indies are senitive on ticks, but for couple seconds at best. After coupe seconds I can open app, bring from the background ect, so the "freeze" is over. This is fully related to my custom indies and how I use them AND perhaps also how cTrader manages "cache" of them. The issue seems to be not exactly about recalculating an indi, but refreshing a window with data history. Naked cTrader works fine and is responsive all the time.
Additional the same setup with cTrader+indis on i7 mobile with 4 core taking 100% of CPU, resulted in 20-30% CPU usage on full i7 with 4 cores, which suggest hardware can be limitation.
So I would say, from my perspective, cTrader performance is on one side limited (obvious) by hardware and on the other side inefficiency of custom indies. cTrader by itself seems to be working fine. I cannot recall situation when cTrader would just freeze and I cannot open it any more and have to close it from the task manager, EXCEPT one that is loaded with a lot of custom indies. The more not optimized indies, the worse performance
Hope that helps with your debugging.