Can you optimize this backtest (speed comparison)
Forums › ProRealTime English forum › ProOrder support › Can you optimize this backtest (speed comparison)
- This topic has 84 replies, 7 voices, and was last updated 3 years ago by GraHal.
-
-
07/01/2020 at 12:20 PM #13789907/01/2020 at 12:32 PM #13790207/01/2020 at 12:57 PM #137907
I prefer not to loose them
I’ll put money on it that backtest be loads faster for you if did not have the 254 Systems stored.
All you need do is export from the backtest window to your PC and hey … you can even store them in Folders for each type of System.
Export takes a few seconds for 3 clicks for each System so 254 would only take 15 – 20 mins tops!
And just as quick to import again when you need them! It’s so liberating! 🙂
07/01/2020 at 1:00 PM #13790807/01/2020 at 1:04 PM #13791107/01/2020 at 1:33 PM #137923So it’s really a “problem” with the PRT plateform.
No. ProOrder servers that handle the automated systems running in live are physically not the same than the ones that make the backtests. So having dozens of running strategies in ProOrder doesn’t affect in any way the backtests duration.
Since no one can replicate the same heavy duration times you have with backtests (here and at ITF), I think that for the moment, you should continue investigating on your side (network, firewall, connection, VPN, .. etc.).
07/01/2020 at 2:32 PM #137930Thanks Nicolas for the informations on differents servers
As I said, I test and have the same results on different computers, different systems (Win7 / Win 10), different connexions, on new Live account, demo account, so it seems not to be due on my side
I don’t understand why it takes 2 minutes wth some people and so many times with others…
@Grahal, no my PRT demo with 254 systems was closed, only the PRT live account
1 user thanked author for this post.
07/01/2020 at 2:42 PM #13793107/01/2020 at 2:46 PM #13793207/01/2020 at 3:02 PM #137933New test : Always the same MTF test version PRT demo 11.1 EUr/USD & mn 100000 units 8000 comb, BUT on another computer, win10 (win7 previoux), different connexion (10 times faster) and…same results
7 mn 5 % only
So the problem is not my computers neither my connexions
The problem should be on PRT server I can’t explain differently ? and may be it could explain how we can have different results if we do tests at different times ?
07/01/2020 at 3:10 PM #137937It’s normal to get different duration during the day depending on the servers charge as you know. But not a so heavy duration that you have.
New test with your MTF code right now: 20% in less than 2 minutes.
Sorry but you are cursed 🙄
07/01/2020 at 3:33 PM #13794907/01/2020 at 4:36 PM #13797207/01/2020 at 6:08 PM #137979Thanks @swedshare
Juste an idea
Can you repeat the test on Eur/usd 100 000 units 8000 comb and do a screen copy of the final results please
Just to confirm something
Thanks
07/01/2020 at 6:13 PM #137980zilliq, I have similar result as swedshare as well. But long time ago, I had some issues with my ISP, its connection were not stable, thus making back test keep resetting.
Would it be worth to do a ping with PRT server? @Nicolas, I assume even computation is done at server, but there is still constant exchange and if the latency is too long, it may slow the back test result as well?
Probably I will start to perform ping to the PRT server and see the ping statistic. Then if way too off chart, to perform tracert to see which route is causing the issue.
From my observation, there are few servers (I didn’t know what are each for and pretty sure live and demo has different servers DNS), I think PRT support could assist you on this, but maybe a first attempt can try to ping ejex.it-finance.com, see if you get better result than below (no loss packet as well):
Pinging ejex.it-finance.com [185.48.201.218] with 32 bytes of data:
Reply from 185.48.201.218: bytes=32 time=191ms TTL=53
Reply from 185.48.201.218: bytes=32 time=191ms TTL=53
Reply from 185.48.201.218: bytes=32 time=187ms TTL=53
Reply from 185.48.201.218: bytes=32 time=187ms TTL=53Ping statistics for 185.48.201.218:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 191ms, Average = 189ms -
AuthorPosts
Find exclusive trading pro-tools on