Topics
Replies
haohan51
11 Feb 2022, 20:31
RE:
PanagiotisCharalampous said:
Hi haohan51,
Can you please try the following?
- - Verify that your OS time is correct
- - install all Windows Updates (especially the ones related to security)
- - Try a Clean Installation of cTrader
Let us know if the above help you resolve the problem
Best Regards,
Panagiotis
Hello thanks for your reply
The issue seemed to automatically resolve itself. I did note that there was a ctrader update that happened, perhaps this was the cause?
@haohan51
haohan51
19 Nov 2021, 14:30
( Updated at: 21 Dec 2023, 09:22 )
RE:
I am not sure it is due to cBot, because I've just had the "not responding" issue when there I had no cBots running at all. Please see screenshot below.
Only difference was that this time it didn't say "Reconnecting". However, it still wasn't displaying the "Live * [Account] * Hedging * £XXX * Leverage" that is usually there if connected properly - suggesting perhaps the connection wasn't correct.
I also opened task manager during this event and you can see CPU usage was not high at all.
The "not responding" period lasted at least 2 minutes, before cTrader finally became responsive again.
As such, I think it is worth investigating on your side?
I have tried to send reports before via Ctrl+Alt+Shift+T, but I have never had a response. How can I send a report and:
1. Link it to this post so you know who it's from
2. Make sure to get a response either on here or via email after submitting using Ctrl+Alt+Shift+T
Thank you
@haohan51
haohan51
19 Nov 2021, 12:10
( Updated at: 21 Dec 2023, 09:22 )
RE:
I managed to catch the incident in the screen shot below.
You can see that:
1. the program is "Not Responding"
2. It is "Reconnecting", suggesting that it is currently disconnected
Does this form of manifestation offer you any clues as to the root of the problem?
Also, are there any diagnostic data for this type of "Not Responding" error that one could look at?
Than you
@haohan51
haohan51
17 Nov 2021, 20:21
( Updated at: 21 Dec 2023, 09:22 )
RE:
Hello Panagiotis,
Thank you for your reply.
I have noted that during the period of mass position/order modification (that happens every 3 minutes), both the CPU cores of the two core VPS goes extremely high in usage, around 99% for moments. You can see this in the screenshot below.
Is this likely the underlying issue?
If so, are you able to make any suggestions?
The code at the moment uses the "Async" method to operate, such as "ModifyPendingOrderAsync" and "ModifyPositionAsync". Does this add extra workload onto the CPU because it's trying to do everything in parallel? Would using non-Async method reduce the CPU load?
Thank you,
Circled in red are the times when positions/orders are being modified (happens every 3 mins).
@haohan51
haohan51
01 Jun 2024, 10:52 ( Updated at: 02 Jun 2024, 11:13 )
RE: RE: RE:
Clark22 said:
Hello, thanks for feedback, but for the benefit of any future reader, I have to push back where I think appropriate.
On cTrader, a Stop Loss is a Market Order and and a Take Profit is a Limit Order (there are some subtleties between different platforms, MT5 is different to cTrader). So no matter where current price is relative to the order price, they are fundamentally different. So this point alone means the statement “If you want to exit trade at a price below current then that's a Stop Loss” cannot be true. I strongly recommend to the reader to go through the illustration in my original post and contrast that to a Stop Loss order.
On the point about “avoiding slippage” - it's worth clarifying that it is possible to avoid slippage but it comes at a cost. The cost being the risk of not getting out at all. So one can absolutely avoid slippage in this sense. In fact, the Take Profit you have (on cTrader) for any position is a Limit Order - which by definition fills at the order price or better. So you shouldn't be getting negatively slipped in a Take Profit. But it's not a free lunch. The danger is that the price never fully crosses or there isn't enough liquidity to get you out at that price/better.
@haohan51