#### Configuration

Global
CPU
Performance
Memory
Databanks
Optimizations
Troubleshooting
Turn off notification sounds
Remember View type and Sorting in File chooser
Show control orders when using MT5 netting engine
Window Header custom text
Window Footer custom text
What result to display on default
Portfolio (if exists)
Main backtest result
This affects which of the results are displayed by default in databank and in Results screen
Garbage collector: ParallelGC (Recommended) G1 Let Java decide
Let program determine maximum memory Set maximum memory to
GB
Don't store unfilled pending orders (Recommended)
It is usually not necessary to keep unfilled pending orders(orders that expired or were replaced). This would make the resulting strategy files smaller.
Perform memory cleanup periodically -
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.
Total cores available {{performance.cores}} Single threaded - program runs tasks sequentially, one after another.
This is slower, but consumes less memory. Reserve 1 core for UI, compute tasks in parallel on all remaining cores. Custom number of cores
Max performance - running multiple tasks in parallel, using all processor cores.
Run StrategyQuant in high priority mode
Use this option ONLY if your SQX doesn't fully utilize your CPU in maximum settings - this could happen with newest processors with P and E-cores.
By using it, SQX process will run in high priority mode, overcoming the efficiency limitations of the system.
Compute metrics in pips (Recommended turned off)
Compute metrics in percent (Recommended turned off)
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.
Compute metrics separate for every data part of the same type
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.
Default auto-sync interval
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.
Synchronize to files automatically after task completion
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.
Save chart data to .sq4 file (not recommended)
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.
Accelerate internal browser using GPU
If you experience problems with GUI, such as freezing or black screen, try turning this off. It will switch to a different rendering method.
Use memory protection - stop projects when 85% of memory is reached
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.
Activate debug level
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.
Don't store data for 3D charts in Optimization profile
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.