Why is backtesting SO slow after the update? yesterday it was fine before I updated and now my cBot is ultra slow
17 May 2024, 08:42
I'm using windows and the backtesting has suddenly become incredibly slow, I even removed the code from my onTick and onStart and it causes no change to the speed. Anyone else having this issue? I wish I didn't update
Can you share your cBot code so that we can reproduce the issue?
Best regards,
Panagiotis
I have the same problem. Unfortunately, I cannot share the bot codes.
During testing, no information is visible in the "Events" tab.
How slow is your backtesting?
It seems to originate from any kind of nested for loops. Or for loops in general. It just hates them suddenly.
im honestly so frustrated ive been working on this project for months and now I can barely get through a day of backtesting since its barely 60x real time
Can you share your cBot code so that we can reproduce the issue?
Best regards,
Panagiotis
I have the same problem. Unfortunately, I cannot share the bot codes.
During testing, no information is visible in the "Events" tab.
How slow is your backtesting?
It seems to originate from any kind of nested for loops. Or for loops in general. It just hates them suddenly.
im honestly so frustrated ive been working on this project for months and now I can barely get through a day of backtesting since its barely 60x real time
why it is not possible to see the bot Optimization progress on the left like before ?! I have to click on each bot now to see if it is being optimized or not unlike the old Ctrader where active optimization where immediately shown by a progress clock on the left so it was easier to quickly identify which bots are still optimizing
why it is not possible to see the bot Optimization progress on the left like before ?! I have to click on each bot now to see if it is being optimized or not unlike the old Ctrader where active optimization where immediately shown by a progress clock on the left so it was easier to quickly identify which bots are still optimizing
And they removed the easily accessible build button… man these were simple quality of life features that were great why did they remove them
Can you share your cBot code so that we can reproduce the issue?
Best regards,
Panagiotis
I have the same problem. Unfortunately, I cannot share the bot codes.
During testing, no information is visible in the "Events" tab.
How slow is your backtesting?
It seems to originate from any kind of nested for loops. Or for loops in general. It just hates them suddenly.
im honestly so frustrated ive been working on this project for months and now I can barely get through a day of backtesting since its barely 60x real time
Can you share your cBot code so that we can reproduce the issue?
Best regards,
Panagiotis
I have the same problem. Unfortunately, I cannot share the bot codes.
During testing, no information is visible in the "Events" tab.
How slow is your backtesting?
It seems to originate from any kind of nested for loops. Or for loops in general. It just hates them suddenly.
im honestly so frustrated ive been working on this project for months and now I can barely get through a day of backtesting since its barely 60x real time
The speed decreased by about 10 times
Ridiculous. I've emailed the given address with my code so hopefully they can find a solution. I moved a lot of my code to onBar but some of it still needs to be in onTick. Anything with a for loop inside of it just makes cTrader go stupid
my bot optimization is also becoming too slow with no possibility to visualize which instances are getting optimzied without click on each one individually..
I can't afford to optimize in such long duration. I am seriously thinking of reverting back to Ctrader 4.8 ( not sure why my Ctrader was actually foreced to update ) !!
my bot optimization is also becoming too slow with no possibility to visualize which instances are getting optimzied without click on each one individually..
I can't afford to optimize in such long duration. I am seriously thinking of reverting back to Ctrader 4.8 ( not sure why my Ctrader was actually foreced to update ) !!
my bot optimization is also becoming too slow with no possibility to visualize which instances are getting optimzied without click on each one individually..
I can't afford to optimize in such long duration. I am seriously thinking of reverting back to Ctrader 4.8 ( not sure why my Ctrader was actually foreced to update ) !!
Now I understand why the platform was presenting bugs all around since the beginning of this month. This is what I call worsening update overall.
my bot optimization is also becoming too slow with no possibility to visualize which instances are getting optimzied without click on each one individually..
I can't afford to optimize in such long duration. I am seriously thinking of reverting back to Ctrader 4.8 ( not sure why my Ctrader was actually foreced to update ) !!
Now I understand why the platform was presenting bugs all around since the beginning of this month. This is what I call worsening update overall.
Basic quality of life features like the quick access build and add instance button in one compartment with the bot was perfect as is. They’ve effectively doubled the size of the damn list of cBots i have because they’ve designated an entire line underneath each bot for add instance. who thought any of this was remotely a good idea? I’ve been working on this project for hours every single day and now it takes over an hour to get through one day of historical tick data are you kidding me? Developers im FURIOUS
my bot optimization is also becoming too slow with no possibility to visualize which instances are getting optimzied without click on each one individually..
I can't afford to optimize in such long duration. I am seriously thinking of reverting back to Ctrader 4.8 ( not sure why my Ctrader was actually foreced to update ) !!
Now I understand why the platform was presenting bugs all around since the beginning of this month. This is what I call worsening update overall.
Basic quality of life features like the quick access build and add instance button in one compartment with the bot was perfect as is. They’ve effectively doubled the size of the damn list of cBots i have because they’ve designated an entire line underneath each bot for add instance. who thought any of this was remotely a good idea? I’ve been working on this project for hours every single day and now it takes over an hour to get through one day of historical tick data are you kidding me? Developers im FURIOUS
rebuild the ALgo using .net 6.0 and enjoy the speed
let me know how it works with you
isnt it always built in 6.0?
Edit: i've always built them in 6.0, the point is it's super slow now suddenly. even after moving most of my code to onBar instead of ontick its still very slow. it wasnt like this yesterday
PanagiotisCharalampous
17 May 2024, 10:37
Hi there,
Can you share your cBot code so that we can reproduce the issue?
Best regards,
Panagiotis
@PanagiotisCharalampous