Tuto WINDEV 25

Part 6: Optimizing and debuging a project 377 Overview The performance profiler (also called Profiler) is a tool used to check and optimize the execution time of the processes found in your application. The principle is straightforward : • You run the test of your application. • During this test, the performance profiler keeps track of all actions performed and saves the execution times of each one of the processes run. At the end of test, the performance profiler displays: • the 10 most time consuming operations, • the duration and the number of calls for all processes run. The "WD Optimization" project contains a specific window used to see the interesting results with the performance profiler. Starting the performance profiler The performance profiler can be started: • from the WINDEV editor : In this case, the project is automatically run in test mode. You can use your application and start the processes of your choice. To go back to the WINDEV editor, all you have to do is exit from your application. Then, the performance profiler displays the monitoring result. This result is saved in a WPF file. • from one of your WLanguage processes , with the following functions: ProfilerStart Starts "collecting data" for the performance profiler. ProfilerEnd Stops "collecting data" for the performance profiler. In this case, only the code found between ProfilerStart and ProfilerEnd is studied. The result is saved in a WPF file.