Hi @all,
I surely not the first one noticing that all this backtesting (especially WF) takes a lot of time and one could work much faster if this could be made faster. Therefore i am wondering where the bottleneck is although I’m afraid the answer might be the PRT server and than there is not much to do about it.
While testing CPU usage is rather low so that is obviously not the problem (so buying a faster PC won’t help).
I’m aware that the way how one is coding affects backtestspeed (thanks to Maz for your recommendations) so no need to point out to optimize my code. 🙂
I got a faster 64 bit PC and upgraded to Fibre broadband .. didn’t make any difference … well maybe a tad faster, but probably due more to more RAM memory on the new PC. Also I get less / zero dropouts now but probably due to change of ISP.
Nicolas says there is a faster BT engine coming later this year.
MazParticipant
Veteran
Computation is done server-side and is heavily throttled per user to ensure fair share of resources.
This was what i thought. Upgrading ones hardware does not help much. OK, so we wait and hope for the new faster engine.