But I don’t understand why it takes only 2 minutes for 60 secondes on the nicola’s computer
Switch off and then log back in again and do the optimise backtest straight away as a first task and tell us if it is any faster?
I say this because I notice that when the RAM used by PRT gets to 2.5 GB ish then it starts getting jittery etc.
I did and it’s the same thing @Grahal
Java takes 2,52 Go in RAM (on 16 Go), so I can’t have less
Can you test with the MTF code even in 10.3, to see, Thanks
wow that code is not really optimized! Same indicator is called multiple times, better to use only 1 variable. You have also used many times the TIMEFRAME instruction to call the same timeframe, also a better idea to organize all the same timeframe codes below only 1 timeframe selection if possible.
Anyway i’m testing it that way and i’m at 5% completed in less than 3 minutes.
Thanks @Nicolas.
Ps: I know it’s not optimized, it’s not the purpose, it’s only to compare time of optimization. And we see MultiFrame slow clearly the optimization (It’s the same code but with MTF)
And we see MultiFrame slow clearly the optimization (It’s the same code but with MTF)
Obviously since the code is way more complex! Also, by using MTF you force X times more data to be loaded (OHLC history in X different timeframes).
Less than 3 minutes for 8,000 combos over 100,000 bars on GBP/USD 15 min TF on PRT v10.3.
With the MTF code ? because it seems very very fast @Grahal
Thanks @zigo
It’s with the MTF version ?, because as Grahal it’s very very fast
I see 100 unit on your picture ?
I’m at 98 % after 1h08 with the MTF version ….EUR/USD 1 mn 100 000 units 8000 combinations
No I guess not … I tested the 1st .itf you posted.
I’ve just scrolled through and seen the 2nd .itf you posted … I will do that one later and report back.
PaulParticipant
Master
mtf version, demo 10.3, mac, 100k bars 1min tf, eurusd, 3m35s
PaulParticipant
Master
and full version 10.3, 100k bars 1m35s