-
Notifications
You must be signed in to change notification settings - Fork 6
Command line parameters
There are several command line parameters to enable/disable features of the profiler.
Parameters are case-sensitive.
-
-profilerAdapterThis lets you choose which "Adapter" aka Frontend you want to use. It's set to Tracy by default which is the most feature rich and performant interface that most people will want to use so you shouldn't need to touch this parameter.
Example:-profilerAdapter Tracy
Possible values:-
Chrome(Chrome Webbrowsers about::tracing page)- Chrome Adapter has a special
-profilerOutputparameter that takes the path to a json file where the profiler will write its data into.
- Chrome Adapter has a special
-
TracyThe Tracy frontend, this is the default. -
BrofilerThe Brofiler interface of the previous iteration of the Profiler, Needs seperate Brofiler GUI binary that won't be provided with newer releases, you should probably not use this. This Adapter is no longer supported. -
ArmaOnly works with the profiling binary of Arma, this is from the first iteration of the Profiler and it opens the Arma Internal profiling display once it captured something and you need to paste a string that was copied to your clipboard. This Adapter is no longer supported.
-
-
-profilerEnableInstructionEnables Instruction Level profiling, displaying every script instruction and every executed script command. This consumes a lot of bandwidth and has a relatively heavy performance impact. Only works if SQF-Assembly addon is available (which is not the case on Linux builds yet). -
-profilerEnableEngineEnables Engine profiling which only works with the Arma profiling binary. This generates a LOT of data, there are sub-parameters to enable some things which are disabled by default to reduce bandwidth requirements.-
-profilerEngineThreadsAlso displays non main-thread zones, these are usually not interesting and eat bandwith so they are default disabled. -
-profilerEngineDoFileEnables zones in the "file" category. There are a lot of file events and most of them are not interesting. -
-profilerEngineDoMemEnables zones in the "memory" category. These are memory alloc/realloc/dealloc and such. Usually not interesting.
-
-
-profilerNoPathsOmits paths to script files, thus reducing required bandwidth and memory. -
-profilerNoInstrumentationDisables automatic instrumentation of every compiled script. -
-profilerEnableFAllocEnables plotting of script type allocation counts, can be used to find memory "leaks". -
-profilerEnableNetworkEnables network profiling