BIS fnc codePerformance: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "\[\[Category\:Function Group\: Debug(\|\{\{[a-zA-Z0-9_:]+\}\})?\]\] " to "") |
Lou Montana (talk | contribs) m (Text replacement - "_{10,} " to "") |
||
Line 1: | Line 1: | ||
{{Function|Comments= | {{Function|Comments= | ||
| arma3|Game name= | | arma3|Game name= | ||
Line 7: | Line 6: | ||
|gr1 = Diagnostic |GROUP1= | |gr1 = Diagnostic |GROUP1= | ||
| [[File:BIS fnc codePerformance.png|300px|right]]Measures how much time it takes to execute given expression. Results may vary based on overall performance; use this function to compare alternative scripting approaches rather than to measure specific values. Upon function execution, window with results is opened. The user then has a choice to copy the result into clipboard or not. <br> | | [[File:BIS fnc codePerformance.png|300px|right]]Measures how much time it takes to execute given expression. Results may vary based on overall performance; use this function to compare alternative scripting approaches rather than to measure specific values. Upon function execution, window with results is opened. The user then has a choice to copy the result into clipboard or not. <br> | ||
Line 14: | Line 12: | ||
Keep in mind that this takes string, and that you can't pass <code>[[str]] _code</code> as string because that add's curly braces to the string. | Keep in mind that this takes string, and that you can't pass <code>[[str]] _code</code> as string because that add's curly braces to the string. | ||
|DESCRIPTION= | |DESCRIPTION= | ||
| [expression, arguments, cycles, display] call [[BIS_fnc_codePerformance]] |SYNTAX= | | [expression, arguments, cycles, display] call [[BIS_fnc_codePerformance]] |SYNTAX= | ||
Line 25: | Line 22: | ||
| [[Number]] - Average execution time of the expression|RETURNVALUE= | | [[Number]] - Average execution time of the expression|RETURNVALUE= | ||
|x1= <code>testArray = []; | |x1= <code>testArray = []; | ||
Line 36: | Line 32: | ||
Compare three methods of adding elements into array|EXAMPLE1= | Compare three methods of adding elements into array|EXAMPLE1= | ||
| [[diag_codePerformance]] |SEEALSO= | | [[diag_codePerformance]] |SEEALSO= |
Revision as of 23:34, 16 January 2021
Description
- Description:
- Measures how much time it takes to execute given expression. Results may vary based on overall performance; use this function to compare alternative scripting approaches rather than to measure specific values. Upon function execution, window with results is opened. The user then has a choice to copy the result into clipboard or not.
This function is using diag_codePerformance command.
Keep in mind that this takes string, and that you can't pass
str _code
as string because that add's curly braces to the string. - Execution:
- call
- Groups:
- Diagnostic
Syntax
- Syntax:
- [expression, arguments, cycles, display] call BIS_fnc_codePerformance
- Parameters:
- expression: String - Tested expression
- arguments (Optional): Anything - Arguments to pass into the code. Default: []
- cycles (Optional): Number - Number of wanted cycles. Default: 10000
- display (Optional): Display - Display in which the message window with results will be opened. Use displayNull to disable the window. Default: Current mission display
- Return Value:
- Number - Average execution time of the expression
Examples
- Example 1:
testArray = []; ["testArray = testArray + [1]"] call BIS_fnc_codePerformance; testArray = []; ["testArray set [count testArray, 1]"] call BIS_fnc_codePerformance; testArray = []; ["testArray pushBack 1"] call BIS_fnc_codePerformance;
Compare three methods of adding elements into array
Additional Information
- See also:
- diag_codePerformance
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note