FxPro - cTrader - Page 4
Page 4 of 734 FirstFirst ... 234
Results 31 to 38 of 338

Thread: FxPro - cTrader

  1. #31
    Quote Originally Posted by ;
    quote Freezes, happens for me when there's a lot of tick per moments and I've a lot of charts open (which are upgraded all at once on each tick.)
    I understand what you mean. I'm familiar with that behavior.
    But that is not it. Like, right now... I had my next cTrader window (with my charts) minimized. And today when I attempt to reactivate the window, then it doesn't start.

    My task manager doesn't label it as non responsive. Everything appears to be fine, except it will not start.

  2. #32
    Just like on Kim's declaration or war? I LIKE THIS GUY

    I had 15 charts, 3 of them with a few good set of indiors ( not yours normal RSI and other vacant. At the most busy time there was approximately 500 ticks per second, so that's 10 ticks per second. Multiply that by 15 and that's 150 ticks each second and all that must be updated o every tick. That is what the program will attempt to do.

    I got roughly 50-60% CPU at i7 mobile. And probably about 30-40% on i7 quarto, but I conduct other stuff on that comp, for every tick also

    However at some point I had full group of charts open with full set of tools and at that point cpu usage was 100%, cTrader was not responsive, hard to switch tab ect. But I consider that normal. It had been very busy time for the app. I can't recall if it act exactly the same way a year or two ago, eventually become batch of recent upgrades. Probably yes.

    After couple minutes ticks came back to approximately 200 per second and my i7 phone is at 30-40%. I7 quarto at 25-30%.

    I also noticed RAM use is rather high. At the moment cTrader utilized about 3Gb. I have 16Gb on such machine, but I guess swap will probably kick in somewhere near. That could be other reason for you, if you have less RAM (?)

  3. #33
    Quote Originally Posted by ;
    quote why don't you trust them?
    Traded XPTUSD / XPDUSD with them, cTrader
    bad rates, slippage

  4. #34
    Quote Originally Posted by ;
    quote traded XPTUSD / XPDUSD together, cTrader bad rates, slippage
    alright thanks to that friend.

    I concur with ActivTrades, ive not had any issues at all.

    Can someone tell me how this works...

    that the low is that the ring on the left... the ring on the right is that the price my trade was closed at...

  5. #35
    Quote Originally Posted by ;
    quote I know exactly what you mean. I'm familiar with that behavior. But that's not it. Like, right now... I had my next cTrader window (with all my charts) minimized. And today when I try to reactivate the window, then it doesn't open. My task manager does not tag it as non responsive. Everything seems fine, except it won't open.
    Oh, I forgot to include: my monitoring are for cTrader platform, but NOT FxPro...

    https://www.forexsoutheast.asia/cryp...t-request.html

  6. #36
    Quote Originally Posted by ;
    Like on Kim's Announcement or war? I LIKE THIS GUY I'd 15 charts, 3 of them with some decent pair of indiors ( not yours typical RSI and other empty. In the busiest time there was about 500 ticks per minute, so that's 10 ticks per second. Multiply this by that and 15 is 150 ticks per second and all that has to be o every tick. That is what the program will attempt to do. I received about 50-60% CPU in mobile. And probably about 30-40% on i7 quarto, but I run other stuff on that comp, for every single tick also ...
    as I mentioned, it's not a PC problem. I have 2, occasionally 3 cTrader windows open with perhaps 20-30 tabs. And one MT4 with some dash indiors.
    CTrader uses maybe 5-10% cpu usually. Even when it's slow and laggy, it's not a hardware performance issue.
    I run 32gig RAM, so no problem at all with running or swap out of ram.

    I did detect some time past, that lots of drawing slow cTrader down aswell, so that I stopped charting every little thing and keep it usually to pairs that I might be considering. Straightforward S/R lines and some fibo.
    My custom indiors are largely refreshed on bar, not tick. I did that just to decrease the load.
    Btw, 95 percent of my tabs are either H4 or D1.

    The problem seems to be largely when cTrader is retained minimized for some time. It can not open and close that is right-click doesn't work.
    I must kill the process and restart it. Then everything is fine.

    Never had this problem until recently.

    I will attempt to watch this a bit more, maybe I figure out exactly where it comes from.

  7. #37
    JeremyV,

    For fascination I did some cTrader evaluations on my i7 laptop. Steps followed.

    Measure A) no cTrader open
    CPU use: 10 percent
    RAM; 2.6Gb

    Measure B) 1x cTrader open with 15 almost naked charts,
    30 minutes prior to London open:
    CPU use: 25 percent
    RAM; 3.0Gb

    Measure C) 2x cTrader open with 15 almost naked charts,
    30 minutes until London open:
    CPU use: 35%
    RAM; 3.3Gb

    Measure D) 2x cTrader open with 15 almost naked charts,
    Plus 1x cTrader using 15 heavy indi charts, 3
    0 minutes prior to London open:
    CPU use: 50-60%
    RAM: 5.2Gb

    Measure E) Leave the installation to run for a while and watch what happens at London open:

    Naked charts cTraders - simple switch between tabs. Heavy indi cTrader - change between tabs lags about 0.5s, but still quite manageable.

    No issue with bringing up minimized cTrader window, some of them.

    CTrader with indis uses about 10x more memory then nude ones. Exactly the same with CPU at time of recalculating indis.

    Following 15 minutes RAM: 5.5Gb

    A while until London open, CPU usage went to 100% temporarily and it required 1-2 moment to deliver back cTrader with indis into front. Not a freeze however. Most of CPU use was alloed to cTrade with indis, which isn't surprising. Naked cTrader are completely responsive.

    Just before London open ticks are getting thicker. CTrader using indis become less responsive - to change tab requires 1-2 second more to perform. Naked cTraders continue to be very responsive.

    Right at London open cTrader with indis become rather unresponsive, CPU use for this cTrader is 80-99% at times. Naked ones continue to be very fine. Yet tick volume for this time is 3-4x higher then before.

    Measure F) 2x cTrader open with 15 almost naked charts,
    Plus 1x cTrader using 15 heavy indi charts,
    10 minutes AFTER London open and 3 apps running for 40 minutes:

    CPU use: 70-80%
    RAM; 5.8Gb

    In summary:

    for me freeze happens using cTrader including a lot of indis. If at precisely the same time many charts are open with many indies, then it will cause temporary freeze. Notice: some of my indies are senitive on ticks, however for couple moments at best. After coupe moments I will open app, bring from the desktop ect, so the freeze is over. This is completely related to my custom indies and the way I use them AND perhaps also how cTrader handles cache of them. The issue appears to be not just about recalculating an indi, but refreshing a window using data history. Naked cTrader works fine and is responsive all the time.

    Additional the same installation with cTrader indis on i7 mobile with 4 core carrying 100% of CPU, led to 20-30% CPU use on total i7 with 4 cores, which suggest hardware could be limit.

    So that I'd say, from my standpoint, cTrader functionality is on one side limited (obvious) by hardware and also on the other hand inefficiency of custom indies. CTrader by itself appears to be working fine. I can't recall scenario when cTrader would just freeze and I can't 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.

  8. #38
    Quote Originally Posted by ;
    quote Oh, I forgot to add: my monitoring are for cTrader platform, but NOT FxPro... https://www.forexsoutheast.asia/gene...ades-lost.html
    Yeh, mine, also. Shouldn't really matter which broker it's, as it doesn't have anything to do with trading requirements.
    Maybe their servers are some Commodore64 somewhere in azshafaghanistan, so their feed pops up, causing cTrader to acquire slow?!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.