Stopping Optimizer when using real tick data takes a long time

Hi,

When optimising using real tick data (which takes a very long time even with fast i7), if you press the stop button, and log says “Stopping….” the actual time it takes to stop the optimisation can be frustratingly long.  Same with tick simulation, but nowhere near as bad as real tick testing.

In SQ4 would it be possible to stop the threads more quickly if the stop button is pressed. It’s like it waiting for all the threads to complete what they are doing, even though the user wants to stop, and this can take many many minutes.

Thanks,

Mike

You can just close SQ and re-open it, that is faster and does the same:)

Are there no lingering files that cause long term problems by closing the app?  (some apps leave temp files, or other things that start to slow down the computer).  

You can just close SQ and re-open it, that is faster and does the same:)

Except it loses all unsaved data and you have to start again.

Terminate it via process manager. Most of time i can reload data but sometimes it is risky

Odoslané z SM-G900F pomocou Tapatalku

Yes, Clonex has right.

But indeed also Mikey has right. Time is very flustrating there, because algorithms has to pass to some period (i don’t know, a every 100?) to stop whole proccess.

Best idea is to install and run 2nd instance of SQ just for optimizing and after such situation feel free to close it via process manager.