The debugger is a powerful tool used to follow the code or application progress, step by step. Enhancing a process or even an application becomes child's play.

We are going to use the debugger on the long process found in the WIN_PerformanceProfiler window.

Using the debugger

To debug the WIN_PerformanceProfiler window:
1. Open "WIN_PerformancepRofiler" in the window editor (double-click its name in the "Project explorer" pane).
2. Run the test of "WIN_PerformanceProfiler" window ( among the quick access buttons).
3. Start the debugger by using one of the following methods:
  - Press Ctrl + [Pause]: the debugger will be automatically started during the next user action in the window whose test is run.
  - Go back to the WINDEV editor and position a breakpoint in the WLanguage code associated to the Button control "Process to analyze" (click next to the first line of code of the "Click" event or press Ctrl + B; a red dot will appear). The debugger will be automatically started when the line preceded by the breakpoint is run.
    Remark
    Several methods can be used to start the debugger.
    See Start modes of debugger for more details.
4. Click "Process to analyze". The debugger starts. The current line is preceded by a little arrow.
  The "Debugger" pane appears in the lower section of the screen. This pane displays two distinct areas:
  - the call stack: This area allows you to know the hierarchy of the events and processes displayed in the debugger. In our example, we are currently debugging the event "Click BTN_LongProcess".
  - the list of expressions to evaluate. By default, the main variables used in the WLanguage code are displayed in this area. You can add variables in order to follow their evolution (this feature will be presented later).

We are going to perform some operations in the debugger to discover its capabilities.

First of all, we are going to run the different statements step by step and see the content of variables:
1. Press the F8 key (or click the "Step by step" button found in the ribbon). The line following the current line is automatically run. The values of variables are modified (if necessary) in the "Debugger" pane (displayed at the bottom of the screen).
2. When the cursor shaped like an arrow reaches the "PROGBAR_Progress..MaxValue = ..." line, hover "PROGBAR_Progress" with the mouse. A tooltip is displayed with the expression value:
3. The value of "PROGBAR_Progress..MaxValue" is displayed in a tooltip. This value corresponds to 100 because the code line was not run.
4. Press F8 to run the line.
5. Hover "PROGBAR_Progress..MaxValue" again. The value of "PROGBAR_Progress..MaxValue" displayed in the tooltip corresponds to the result of HNbRec(Product).

Let's continue our operations in the debugger. We are now going to run the UpdateProductStock procedure step by step in the debugger.
1. To run this procedure step by step, press the F7 key (or click the "Detailed step by step" button in the ribbon).
2. The procedure code is displayed in the debugger.

We are now going to add an expression to monitor the evolution of its value in the "Debugger" pane. This expression can have any type: variable, function, operation on variables, ... The expression result is calculated and displayed.

This expression is used to perform a custom debugging. For example, you can find out the content of a variable while it is being used in the application.

Press F7 to run the different lines of UpdateProductStock procedure until you reach the line:
PROGBAR_Progress++
Hover "PROGBAR_Progress". The value displayed in the tooltip is 0.
Select "PROGBAR_Progress" in the code editor and open the popup menu (right click). Select "Add expression to debugger".
The expression is automatically added into the debugger pane at the bottom of the screen.

The debugger can also be used to run a set of code lines:
1. Press F8 until you reach the line:
  HModify(Product)
  The F8 key is used to run the code of InterrogateSupplierDatabase procedure without running it step by step in the debugger.
2. Click the following line with the mouse (caution: click inside the line and not in front of it):
  IF HExecuteQuery(QRY_QuantityOrdered) THEN
3. Press the F6 key (or click the "Run until cursor" button found in the ribbon).
4. The arrow indicating the line currently run moves until it reaches the code line where the cursor is positioned. The code lines found before the cursor are automatically run.

We are now going to add a breakpoint and to run the code until it reaches the breakpoint:
1. Click in the hatched area with the mouse, in front of HModify. A breakpoint (red bullet) appears.
2. Press F5 (or click "Continue" in the ribbon). The code is run until it reaches the breakpoint. The arrow used to identify the current line moves until it reaches the breakpoint.
3. Click the breakpoint to remove it.

To end this test, we will be using an "Auto-stop" expression. An "Auto-stop" expression is used to start the debugger as soon as a condition is checked or when the value of a variable is modified. In our example, the debugger will be started as soon as the value of progress bar is set to 50%:
1. In the "Debugger" pane, select the "PROGBAR_Progress" expression that was added beforehand.
2. Click the green circle.
3. Press F5 to continue the test.
4. A message is displayed, indicating that the value of "PROGBAR_Progress" expression changed.
5. Validate.
6. In the "Debugger" pane, select the "PROGBAR_Progress" expression. Click the expression again: the "Expression" column becomes editable. In the "Expression" area, add "=50". You will get "PROGBAR_Progress = 50".
7. Press F5. The program continues to run. The debugger is started again when the value of the progress bar is set to 50.

That's it, the main features of debugger have been presented here. To stop the test in the debugger, click "End the test" found in the ribbon.

sexta-feira, 28 de agosto de 2020

DICAS 3056 - WINDEV TUTORIAL 79 -04-09-2020 11Hrs- OTIMIZAR ANALISADOR DE DESEMPENHO

w3HJ3X-PnSA

Bom Dia/Boa Tarde/Boa Noite

Esse Ao Vivo vai estrear as 11:00 do dia 04/09/2020

DICAS 3056 - WINDEV TUTORIAL 79 -04-09-2020 11Hrs- OTIMIZAR ANALISADOR DE DESEMPENHO

Tutoriel WINDEV : Leçon 6.3. Optimiser et déboguer - Analyseur de performances

https://windevdesenvolvimento.blogspot.com/2020/08/dicas-3056-windev-tutorial-79-04-09.html

ASSUNTOS

VAMOS VER O QUE SERA ENSINADO

VISAO GERAL

O QUE PROFILER

INICIANDO O PERFIL DE DESEMPENHO

DUAS OPCOES

PELO EDITOR WINDEV

POR PROGRAMACAO

profillerstart

profillerend

INICIANDO TESTE DE DESEMPENHO

ESTUDANDO O RESULTADO

https://doc.windev.com/en-US/?1410087546&name=lesson_63_performance_profiler

Video original da Franca

https://youtu.be/wdYlVdAzE5I

Playlist Windev TUTORIAL

https://www.youtube.com/playlist?list=PLwJwZaqiZW-lxU1XF0M0htb5S5f8pavuE

Repositorio Windev

https://repository.windev.com/

https://youtu.be/3DshsXJ8I2M

https://youtu.be/EqnYJFpvPAI

DICAS 3008 - WINDEV TUTORIAL 31 - Adicionar e Modificar Janelas ANCORAS - PARTE D
DICAS 3009 - WINDEV TUTORIAL 32-Adicionar e Modificar Janelas - Exibicao registro - PARTE E

DICAS 3010 - WINDEV TUTORIAL 33-Adicionar e Modificar Janelas - Modifica Imagen - PARTE F

DICAS 3011 - WINDEV TUTORIAL 34 - Adicionar e Modificar Janelas - Validacao - PARTE G

DICAS 3012 - WINDEV TUTORIAL 35 - Adicionar e Modificar Janelas - CRIACAO - PARTE H

DICAS 3013 - WINDEV TUTORIAL 36 - Adicionar e Modificar Janelas - Teste - PARTE I

DICAS 3014 - WINDEV TUTORIAL 37 - Pesquisa Simples - Apresentacao - PARTE A

DICAS 3015 - WINDEV TUTORIAL 38 - Pesquisa Simples - Usando Controle Tab- PARTE B

DICAS_3016_WINDEV_TUTORIAL_39_Pesquisa_Simples_Configurando_Pesquisa_PARTE_C

DICAS 3017 - WINDEV TUTORIAL 40 - Pesquisa Simples - Pesquisa Identica- PARTE D

DICAS 3018 - WINDEV TUTORIAL 41 - Pesquisa Simples - Pesquisa Generica - PARTE E

DICAS 3019 - WINDEV TUTORIAL 42 - Pesquisa Simples - Navegacao pelos Arquivos - PARTE F

DICAS 3020 - WINDEV TUTORIAL 43 - Pesquisa Multicriterio - Apresentacao - Parte A

DICAS 3021 - WINDEV TUTORIAL 44 - Pesquisa Multicriterio - Criacao Consulta - Parte B

DICAS 3022 - WINDEV TUTORIAL 45 - Pesquisa Multicriterio - Uso Parametro - Parte C

DICAS 3023 - WINDEV TUTORIAL 46 - Pesquisa Multicriterio - Criando Interface - Parte D

DICAS 3024 - WINDEV TUTORIAL 47 - Pesquisa Multicriterio - Primeiro Parametro - Parte E

DICAS 3025 - WINDEV TUTORIAL 48 - Pesquisa Multicriterio - Segundo Parametro - Parte F

DICAS 3026 - WINDEV TUTORIAL 49 - Pesquisa Multicriterio - Parametro Data - Parte G

DICAS 3027 - WINDEV TUTORIAL 50 - IMPRIMIR_TABELA

DICAS 3028 - WINDEV TUTORIAL 51 - IMPRIMIR PEDIDO-CRIACAO RELATORIO - PARTE A

DICAS 3029 - WINDEV TUTORIAL 52 - IMPRIMIR PEDIDO - CRIAR O RELATORIO BASE QUERY - PARTE B

DICAS 3030 - WINDEV TUTORIAL 53 - IMPRIMIR PEDIDO - ALTERACOES RELATORIO - PARTE C

DICAS 3031 - WINDEV TUTORIAL 54 - IMPRIMIR PEDIDO - MENU RELATORIO - PARTE D

DICAS 3032 - WINDEV TUTORIAL 55 - RELATORIO LISTA CLIENTE - PARTE A

DICAS 3033 - WINDEV TUTORIAL 56 - RELATORIO CLIENTE - Imprimir - PARTE B

DICAS 3034 - WINDEV TUTORIAL 57 - ESTATISTICAS GRAFICO PIVOT - QUERY ANO - PARTE A

DICAS 3035 - WINDEV TUTORIAL 58 - ESTATISTICAS GRAFICO PIVOT - GRAFICO-PARTE B

DICAS 3036 - WINDEV TUTORIAL 59 - ESTATISTICAS - PIVOT - PVT - PARTE C

DICAS 3037 - WINDEV TUTORIAL 60 - ENVIAR EMAIL - ADICIONANDO CAMPOS - PARTE A

DICAS 3038 - WINDEV TUTORIAL 61 - ENVIAR EMAIL - CODIGO - PARTE B

DICAS 3039 - WINDEV TUTORIAL 62 - ENVIAR EMAIL - MELHORIAS - PARTE C

DICAS 3040- WINDEV TUTORIAL 63 - GROUPWARE - CONFIGURACAO - PARTE A

DICAS 3041- WINDEV TUTORIAL 64 - GROUPWARE - TESTE - PARTE B

DICAS 3042- WINDEV TUTORIAL 65 - COMPONENTES EXTERNOS - CRIANDO - PARTE A

DICAS 3043 - WINDEV TUTORIAL 66 - COMPONENTES EXTERNOS - USANDO - PARTE B

DICAS 3044 - WINDEV TUTORIAL 67 - CONSUMINDO SERVICO WEBSERVICE

DICAS 3045 - WINDEV TUTORIAL 68 - MONITORAR EVOLUCAO SEUS APLICATIVOS - TESTES

DICAS 3046 - WINDEV TUTORIAL 69 - DEPLOYING APPLICATION CRIANDO EXECUTAVEL PARTE A

DICAS 3047 - WINDEV TUTORIAL 70 - DEPLOYING APPLICATION CRIANDO INSTALADOR PARTE B

DICAS 3048 - WINDEV TUTORIAL 71 - DISTRIBUIAO RELATORIOS QUERIES-CONSULTAS

DICAS 3049 - WINDEV TUTORIAL 72 - GERENCIAMENTO VARIOS IDIOMAS

DICAS 3050 - WINDEV TUTORIAL 73 - SCM

DICAS 3051 - WINDEV TUTORIAL 74 - HYPERFILE CONCEITO INSTALACAO PARTE A

DICAS 3052 - WINDEV TUTORIAL 75 - HYPERFILE - CONFIGURANDO SERVIDOR - PARTE B - 03-09-2020 14Hrs

DICAS 3053 - WINDEV TUTORIAL 76 - HYPERFILE GERENCIANDO SERVIDOR - PARTE C - 03-09-2020 16Hrs

DICAS 3054 - WINDEV TUTORIAL 77 -03-09-2020 18Hrs- HYPERFILE INSTALANDO EM CLIENTE - PARTE D -

DICAS 3055 - WINDEV TUTORIAL 78 -04-09-2020 09Hrs- PROJETO OTIMIZAR E DEPURAR

DICAS 3056 - WINDEV TUTORIAL 79 -04-09-2020 11Hrs- OTIMIZAR ANALISADOR DE DESEMPENHO

DICAS 3057 -WINDEV TUTORIAL 80 -Licao 6.4-04-09-2020 14Hrs- Debugging a project

Lesson 6.3. Performance profiler

This lesson will teach you the following concepts

Overview.
Starting the performance profiler.
Studying the result.


	Estimated time: 15 mn

Previous Lesson

Table of contents

Next Lesson

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.

The first method will be used in our example. To start the performance profiler on the "WD Optimization" project:

On the "Project" pane, "Audit and performance" group, expand "Analyze performance" and select "Analyze performance".


	Remark	The performance profiler can also be started from the project dashboard, via the "Performance" widget. Simply: enable the Widget if necessary (click the link "Click here to re-enable"). expand the button with arrow and select "Analyze the performance".

The project test is run.
Click the "Test window of performance profiler" button.
Click the "Process to analyze" button.
Validate the information window and stop the project test. The performance profiler report window appears.

Studying the result

Let's study the report window of the performance profiler. Results are displayed in several tabs:
- the "Summary" tab presents the ten longest processes.
- the "Mapping" tab presents a graphical view of main processes.
- the "Details" tab presents all processes run during the application test (from the slowest one to the fastest one).
- the "Calls" tab is used to view the details of operations performed in a process.

Let's present these different tabs in our example.
- The "Summary" tab presents the ten longest processes. In our example, you can see that the local procedure named "UpdateProductStock" takes more than 3 seconds to run.
- The "Mapping" tab is used to visually identify what took the longest time. In our case, it's a call to Ping:
- The "Details" tab presents all processes or events run, from the slowest one to the fastest one.
  The following information is displayed for each process or event:
  - Function: Function, event or procedure run.
  - Total time: Execution time of function.
  - Internal time: Execution time due to the engine.
  - Nb of calls: Number of calls made to the function (procedure or event).
  - Time 1 call: Execution time of a call to the function (procedure or event).
  - Code %: Percentage of time spent in the process of function or procedure (developer code that can be optimized).
  - Parent: Element that contains the process.

In our case, the "Details" tab indicates that the call to the "Ping" function is one of the elements taking the longest time.
1. Select this line. We are going to check whether this slowdown is caused by a specific problem.
2. Click the "Calls" button to display the details of calls to the UpdateProductStock procedure. Select the "Ping" line and click the "Code" button: the corresponding code line is displayed in the code editor.
3. Close the performance profiler.
4. The following code line is run:
  // Checks the accessibility of supplier server
  Ping("supplier-addr")
  The slowdown is caused by the fact that the address specified for Ping is not accessible.

Let's check the operating mode of application by optimizing this code:
1. Replace the code line containing Ping by the following code line:
  // Checks the accessibility of supplier server
  Ping("www.google.fr")
2. Save the code (Ctrl + S).

We are now going to restart the performance profiler:
1. On the "Project" pane, "Audit and performance" group, expand "Analyze performance" and select "Analyze performance".
2. The project test is run.
3. Click the "Test window of performance profiler" button.
4. Click the "Process to analyze" button.
5. Validate the information window and stop the project test. The performance profiler report window appears.
6. In the "Mapping" tab, Ping does not appear with the same importance.