I have the same exact problem with an Azure Virtual machine. Connecting via remote desktop it reduces the CPU usage to 33%.
It is quite easy to be tested. Run any optimization test on the bot. Leave it running and disconnect from remote desktop (ensure you have the CPU usage at 100%). Reconnect and see the slider has gone to 33%…
Unfortunately due to such issue we can't optimize bots that could take up to a week or more to be optimized (as in this case it will take 3 weeks)…
Thank you, it works fine for me and there was no similar report, so it seems like a local issue. Try refreshing using Ctrl+F5 in case something has been cached
To make sure @Spotware sees this, please also report this issue and link to thread via the cTrader desktop app:
Thanks!
I just reported the error even though there was a character limit on the Report Technical Issue page and I had some difficulty as the limit doesn't allow you to copy-paste any source code larger than a few lines.
Bars are constructed exclusively on bid prices. Therefore the outcome you describe is expected. A suggestion would be to just loop over the ticks collection and check which price was changed (bid or ask) and increase the relevant counter accordingly.
I am not quite sure if any of the suggestions (mine or yours) should be correct.
Without being an expert in trading, I guess that there could be a sale or a buy that doesn't change either the bid or the ask.
Hypothetically, someone is bidding 200 stocks of MSFT at $204. Then someone sells 50 stocks of MSFT at $204. I imagine that at that point, the bid price shouldn't change as there are some 150 stocks remaining to be bought. Also, since a lot of brokers have usually fixed spreads, the ask will not change too.
Am I wrong in what I say?
If that is the case, then we can never be sure that the order that happened was a sale or a buy.
So... I am wondering how all these volume profile indicators for cTrader work and if they display correct values.
This website uses cookies to enhance site navigation, analyze site usage, and assist in our marketing efforts. By clicking “Accept All” you are providing your consent to our use of all cookies. Alternatively, please provide your choice by pressing “Customize Cookies”. For more information, please read our Privacy policy
ekalyvio
25 Jan 2025, 11:54
The problem is not solved…
I have the same exact problem with an Azure Virtual machine. Connecting via remote desktop it reduces the CPU usage to 33%.
It is quite easy to be tested. Run any optimization test on the bot. Leave it running and disconnect from remote desktop (ensure you have the CPU usage at 100%). Reconnect and see the slider has gone to 33%…
Unfortunately due to such issue we can't optimize bots that could take up to a week or more to be optimized (as in this case it will take 3 weeks)…
@ekalyvio