• the 10 most time-consuming operations
• all actions performed in the application that was tested, sorted by duration (from the longest to the shortest action).

The performance profiler does not work with an AWP site.

Starting the performance profiler

• Directly from the WINDEV, WINDEV Mobile or WEBDEV editor In the "Project" pane, in the "Audit and performance" group, scroll down to "Analyze performance" and select "Analyze performance". In this case, the project is automatically executed in test mode. The process to optimize can be run in your application.
  To go back to the editor of WINDEV, WINDEV Mobile or WEBDEV, simply exit your application or site.
  The performance profiler displays the result of the analysis. This result is saved as a WPF file.
  The test is run in the simulator.
• From one of your WLanguage processes, with the following functions:
  

  ProfilerEnd	Stops "collecting data" for the performance profiler.
  ProfilerStart	Starts "collecting information" for the performance profiler.

  In this case, only the code between ProfilerStart and ProfilerEnd will be analyzed. The corresponding WPF file can be opened in the performance profiler: under the "Project" pane, in the "Audit and performance" group, pull down "Analyze performance" and select "Open performance report".
• During debugging thanks to performance analysis between two breakpoints. All you need to do is set the start and end breakpoints for the performance profiler. Only the code between these two breakpoints will be analyzed. The report is automatically displayed in the editor at the end of the analysis. For more details, see Breakpoints.
• From any application Press the key combination WIN + Shift + F10 has the same effect as calling function ProfilerStart.
  In this case, you can terminate the analysis by closing the application, or by pressing the Windows logo key + Shift + F11.
  When the recording stops, the location of the analysis report is copied to the clipboard.

• We recommend using the performance profiler to optimize your application (before release, for example).
• If the "Performance" widget is enabled in the Project dashboard, the performance profiler is automatically started whenever the project is tested (via "GO"). The corresponding performance report is saved in the project directory. If a problem occurs, a click on the link "Click here to see the details" allows you to display the performance report.

Saving or opening a statistical file

1. On the "Project" tab, in the "Audit and performance" group, expand "Analyze performance" and select "Open a performance report".
2. Specify the path and name of the statistics file.

Reading the performance profiler results

• the "Synthesis" tab presents the 10 longest processes.
• the "Details" tab shows all the processes run during the test of the application (from the slowest to the fastest).

The following information is displayed for each process:

	Parent	Element or process that called the function.
	Function	Function, process, event or procedure run.
	Total time	Function execution time.
	Calls	Number of calls made to the function (procedure, event or process).
	Time per call	Execution time of a call to the function (procedure, event or process)
	% code	Percentage of time it took to process the function or procedure (developer code that can be optimized).

• "Full execution" represents the total execution time of the application test in the performance profiler.
• "Total for XXX Window" represents the total execution time of a given window (from the moment it is opened until closed).

Choosing a process to optimize

• The process execution time. The longest processes must be optimized.
• The percentage of time spent in the process of the function or procedure. The higher this percentage is, the greater the number of processes that can be optimized in the code.

Optimizing a process

1. Select the function to optimize in the "Details" tab.
2. Display the details of this function:
   • double-click the function.
   • click the "Calls" button.
3. The following tab is displayed:
   
   This tab is divided into three sections:
   • The list of functions calling the selected process.
   • The selected function (with the number of calls to this function and the total processing time).
   • The list of functions called by the selected function.

• The "Internal process of runtime engine" caption corresponds to the execution time of the function or procedure (for a WLanguage function for example). This time cannot be reduced and it cannot be optimized.
• The "Developer code" caption corresponds to the execution time of the function or procedure. This time can be reduced and it can be optimized.
• To quickly view the current process, all you have to do is click . The profiler remains opened and the current code can be modified.
• The "Previous" button is used to go back to the calling function.
• The "Start" button is used to go back to the process found at the beginning of the application.
• If the application includes several threads, only the main thread is taken into account.