Parametereinstellung Arma 3 - Launcher

-cpuCount= is option which allows define number of CPUs/cores available.

-exThreads= is option to define extra threads.

All file operations go through a dedicated thread. This offloads some processing from the main thread,

however it adds some overhead at the same time.

The reason why threaded file ops were implemented was to serve as a basement for other threads ops.

When multiple threads are running at the same time, OS is scheduling them on different cores.

Geometry and Texture loading (both done by the same thread) are scheduled on different cores

outside the main rendering loop at the same time with the main rendering loop.

Ex(tra)threads table Number Geometry loading Texture loading File operations

0-----------------------------------------0-------------------------0----------------------0

1-----------------------------------------0-------------------------0----------------------1

3-----------------------------------------0-------------------------1----------------------1

5-----------------------------------------1-------------------------0----------------------1

7-----------------------------------------1-------------------------1----------------------1

Enables the use of all logical CPU cores for parallel tasks processing. If your CPU does not support Hyper-Threading

or similar technology, this parameter is ignored. When disabled, only physical cores are used.Note that enabling this

parameter may slightly improve or harm the performance depending on a scenario. This parameter may be overriden by

-cpuCount so if you want to use the maximum number of CPU cores use "-enableHT" without "-cpuCount".

-malloc=<string> Sets the particular memory allocator to be used. Significantly affects both performance and stability of the game.

Link: Bistudio: Custom Memory Allocator

Google Malloc: TCMalloc and PTMalloc

Enables hugepages with the default memory allocator for both client/server Bistudio: Performance-Binary-Feedback

-maxMem=<number> Overrides memory allocation limit to a certain amount (in megabytes).

1024 MiB is a hard-coded minimum (anything lower falls back to 1024). The maximum is influenced by your operating system

(any value over the maximum will be reverted to this value):

32-bit Windows + 32-bit game: 2047

64-bit Windows + 32-bit game: 3071

64-bit Windows + 64-bit game: (physical memory*4)/5

Without the -maxMem parameter the engine attempts to set this parameter internaly to a reasonable value often defaultingto max values as described above.The file cache is always excluded from the virtual address limit,

see our developers blog: breaking-the-32-bit-barrier.

Note that setting maxMem to 2000 does not mean that the game will never allocate more then 2000 MiB.

It says that the game will do everything in its power to not cross this limit.

In general, it makes sense not using this parameter at all and only resort to it in case you experience issues with memory.

-maxVRAM=<number> Defines Video Memory allocation limit to number (in megabytes).

Use to resolve e.g. Windows problem.

Minimum value is 128 MiB (anything lower falls back to 128). The value is ignored (under DX11) if engine properly detected VRAM size,

minus 20% reserve with ceiling limit 300MB max.