It is usually not necessary to keep unfilled pending orders(orders that expired or were replaced). This would make the resulting strategy files smaller.

Clean memory periodically by explicitly calling Java Garbage Collector.
Use it if you experience problems with memory, otherwise keep it turned off.
Java does this automatically and it usually does a very good job.
Turning it on without reason might slow down the application.

In addition to metrics in money, also metrics for % and pips results can be computed. It is generally recommended to have it turned off. Most people don't need these results and not computing and storing them will improve speed and memory consumption.

Turning this on means that if you have your data divided into multiple OOS parts, for example OOS1, OOS2, OOS3, OOS4 - then the metrics like Net profit etc. will be computed also separately for each of these parts.

This enables you to see these metrics separately in Results or databank, or use them in conditions but it also slows down the program and uses more memory.

On by default, turn it off if you don't use it. Whole OOS metrics are always computed.

Databanks keep strategies in memory for fast access.
They can be automatically synchronized to the disc in a preconfigured interval so that there is a backup in in case of program crash. Don't synchronize them too often though, it negatively impacts the performance.

Settings here are applied to all newly created databanks. If you want to apply them to all the existing databanks click on the button below.

If on, strategies in task's output databank will be saved to files automatically after the task is done.
No restart needed for this setting to take effect.

If on and you have configured to Store Chart Data in Trading Options, trades on chart are saved to .sq4 file. This makes the resulting file much bigger, but it allows you to view Trades on chart later.

If off, chart data are kept only temporarily and will be thrown away when not used.
You'll have to retest the strategy to get the chart data again.

If you experience problems with GUI, such as freezing or black screen, try turning this off.It will switch to a different rendering method.

This will stop your projects when SQ reaches 85% of memory usage.
It prevents program from freezing and being unresponsive.
Turn it on if you experience program freezes.

By turning this on you'll activate debug logging level. Debug level should be used only when investigating some problem, it is much slower and produces very large log files.

Turned on by default, it saves a lot of memory both in RAM and in disk files
when working with Optimizations (simple or WF).

Data required for 3D optimization charts are very big and are usually not needed at all.
This does not affect other functionality of Optimization profile - filtering
and conditions will work as usual.
It also has nothing to do with Walk-Forward results charts.

To show 3D optimization charts just reoptimize the strategy with this setting off.