Don't optimize with real ticks over a long period.
This means a huge amount of data regardless which timeframe you are using packed in the RAM. If you now use all your kernels twice due to hyperthreading the pc starts immediately with an extensive swapping - have you watched the led of the hd access - anything else dies on the pc.
I'm complaining about this issue allready a very long time and I'm optimising with 1 minute bars over 3 years of data. I've noticed that with latest releases (I'm using beta 2652), the problems are much less than before.
But there's still a memory management problem in the backtester. I have a AMD Ryzen 9 3900x with 32 GB RAM and very fast SSD. The problems arise when you optimise with a lot of passes.
Agents do not work with DLL's ..
I am using custom symbols, going back 3 years, with about 25 passes per optimization. Even with just every tick modelling it still instantly shoots my ram up to 100%. It has always done this and normally it is fine, but recently after a while it freezes my pc completely and I have to restart.
I have 2 PC' s with AMD Ryzen 9 3900x, 32 GB RAM and a very fast SSD (1 T) both with Beta release 2656.
Durinng the optimising one PC generates memory problems and does not (only 3 passes) continue with optimising.
My other PC with exactly the same software but another currency continues optimising (96 passes) and generates no problems.
This illustrates very clearly the problems with the memory management during the optimising proces.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.