WEBDEV Concepts

200 Part 6: Testing a Web site Remarks : • The trace file is created by default in the user data directory. The name of this file is the same as the project name. This file contains the information to trace during the program execution. The information is completed by the date and time of each "Trace". This allows you to detect a potential problem during the process. • Example of trace file content: 01/12/2015 - 10:53:25:20 Customer name: Montgomery 6 Performance test 6.1 Overview The performance profiler allows you to check and optimize the execution time of your site. The principle is straightforward: • You test your site. • During the test, the performance profiler keeps track of all the actions performed and the corresponding processes run. At the end of the test, the performance profiler displays: • the 10 most time-consuming operations. • all the actions performed in the tested site, sorted by duration (from the longest to the shortest action). You can select a process to analyze its processing time and optimize it. 6.2 Starting the performance profiler To start the performance profiler, go to the "Project" tab, "Audit and performance" group, expand "Analyze performance" and select "Analyze performance". The project is automatically run in test mode. The process to optimize can be run in your site. To go back to the editor, all you have to do is close your application or your site. Then, the performance profiler displays the result of the analysis. Remark : The performance profiler should be used to optimize your site (before it is distributed for example). 6.3 Reading the performance profiler results The performance profiler presents the result of the analysis in several tabs: • the "Summary" tab shows the ten longest processes. • the "Mapping" tab shows a graphical view of the main processes. • the "Details" tab shows all the processes run during the test of the application (from the slowest to the fastest). • the "Calls" tab shows the details of the operations performed in a process. The following information is displayed for each process: Function Function, process or procedure run. Total time Function execution window. Nb of calls Number of calls made to the function (procedure or process). Time 1 call Execution time of a call to the function (procedure or process). code % Percentage of code run outside the call to a WLanguage function or outside the call to a custom function or procedure. Parent Process that called the function. Remark : • The "Full execution" caption represents the total amount of time for running the site test with the performance profiler. • The "Total Page XXX" caption represents the total amount of time for running the page XXX (from its opening to its closing).