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.

Close the performance profiler report window.

ErpMatos - TgsSistemas

skype:amarildo.matos.informatica

email: amarildo.matos@gmail.com

whats: 51984197742

Youtube: Amarildo Matos

http://www.amarildomatos.com.br

https://groups.google.com/forum/#!forum/amarildowindev

www.windev.com

https://www.pcsoft.fr/webinaires.htm?p=forumpcs

https://forum.pcsoft.fr/fr-FR/pcsoft.br.windev/page/1.awp

https://www.windev.com/windev/WD-Express.htm

https://www.windev.com/windevmobile/WM-Express.htm

http://windevdesenvolvimento.blogspot.com.br/2017/07/menu-blog.html

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

jT504xmXnP0

Bom Dia/Boa Tarde/Boa Noite

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

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

Tutoriel WINDEV : Leçon 6.2. Optimiser et déboguer - Audits du projet

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

ASSUNTOS

MUITO TOP, NAO USAVA E AGORA VOU USAR

O QUE VAMOS APRENDER NESSA LICAO

O QUE É UMA AUDITORIA ESTATICA E DINAMICA

MOSTRANDO AUDITORIA ESTATICA

ENTRANDO NO PROJETO OTIMIZA E ENTRANDO AUDITORIA

ESCOLHENDO AUDITORIA TODO PROJETO

EXPLICANDO O QUE APARECEU NOS RESULTADOS DA AUDITORIA

EXPLICANDO QUANDO TEM UM CODIGO QUE NAO SE USA MAIS

MOSTRANDO ELEMENTO ORFAO, JANELA NUNCA CHAMADA

FAZENDO LIMPESA DE ARQUIVOS NAO UTILIZADOS NO PROJETO

ERRO DE VERSAO E ARRUMANDO

EXPLICANDO AUDITORIA DINAMICA

EXECUTANDO O TESTE

EXPLICANDO O TESTE

EXPLICANDO COMO FAZER ESSA AUDITORIA EM CLIENTE

https://doc.windev.com/en-US/?1410087545&name=lesson_62_project_audits

Video original da Franca

https://youtu.be/Nihd09vTHeY

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

ErpMatos - TgsSistemas

skype:amarildo.matos.informatica

email: amarildo.matos@gmail.com

whats: 51984197742

Youtube: Amarildo Matos

http://www.amarildomatos.com.br

https://groups.google.com/forum/#!forum/amarildowindev

www.windev.com

https://www.pcsoft.fr/webinaires.htm?p=forumpcs

https://forum.pcsoft.fr/fr-FR/pcsoft.br.windev/page/1.awp

https://www.windev.com/windev/WD-Express.htm

https://www.windev.com/windevmobile/WM-Express.htm

http://windevdesenvolvimento.blogspot.com.br/2017/07/menu-blog.html

Lesson 6.2. Project audits

This lesson will teach you the following concepts

What is an audit and what is its purpose?
Starting and studying the static audit.
Starting and studying the dynamic audit.


	Estimated time: 15 mn

Previous Lesson

Table of contents

Next Lesson

What is an audit?

Audits provide a set of features that allow you to:

automatically improve the quality and performance of a project.
monitor the conditions in which it operates more precisely.

Two types of audits are available:

The static audit. The static audit performs a detailed analysis of a project and elements. This audit is performed from the project editor.
The dynamic audit. The dynamic audit analyzes the behavior of a project during its execution. This audit can be performed in test mode or in the production environment.

We are going to check these audits on the "WD Optimization" project.

Static audit

The static audit is an environment feature used to study the source codes of a project in order to detect different problems and to propose improvements.

To start the static audit on the "WD Optimization" project:

On the "Project" pane, in the "Audit and performance" group, expand "Edition audit" and select "Trigger the audition audit".


	Remark	The static audit of project can also be started from the project dashboard, via the "Static audit and Compilation" widget. To do so: enable the Widget if necessary (click the link "Click here to re-enable"). click the arrow.

The wizard starts. We are going to define the target of static audit.
Select "Run the static audit on the entire project".
Validate the wizard.
The audit report is displayed:

The static audit includes:

The static audit of project.
The audit for the content of application library.
The audit of setup content.

Let's study the topics presented by this report.

Procedure not run

In our project, the audit indicates that a procedure is never run.

In huge projects, you may want to create one or more procedures to perform a process then, further to a code reorganization, the procedure is no longer used but it remains in the project. The presence of unused procedures unnecessarily consumes the resources distributed to the end users.

To fix this problem:
1. Click the [...] button to get more details. The window that lists the dead codes is displayed.
2. The "ObsoleteProcedure" procedure is never called. This window is used to:
  - specify that the procedure is still used ("Flag as useful"). In this case, the procedure will not be taken into account anymore during the audit.
  - delete the procedure if it is actually unused ("Delete").
  - see the procedure ("View").
  - find the use cases in the strings for example ("Search").
3. In our case, this procedure is actually unused, click "Delete".
4. A window is displayed, asking you to confirm the deletion. Click the "Delete" button to confirm the deletion.
5. Close the window of dead code (click the cross in the top right corner).

In the window of static audit, click the "Refresh" button to update the audit report.

Orphan element

The audit indicates that our project contains an orphan element.

As for the procedures run, you may create windows or reports in order to run a quick test, save them and forget everything about them. The presence of orphan elements in the executable unnecessarily consumes the resources distributed to the end users.

To fix this problem:
1. Click the [...] button to get more details. The window that lists the orphan elements is displayed.
2. The "WIN_UnusedWindow" window is never called. The window that lists the orphan elements is used to:
  - specify that the element is still used ("Flag as useful"). In this case, the window will not be taken into account anymore during the audit. This option can be interesting when using a test window specific to the development for example.
  - delete the element if it is actually unused ("Delete").
  - see the element ("View").
  - find the use cases in the strings for example ("Search").
3. In our case, this "WIN_UnusedWindow" window is actually unused, click "Delete".
4. Close the window of orphan elements (click the cross in the top right corner).

In the window of static audit, click the "Refresh" button to update the audit report.

Cleaning the project

Our project contains several unused files. You have the ability to clean the project in order to keep the necessary elements only. The executable and the client setup is not weighted with images, external files, ... not used.

To fix this problem:
1. Click the [...] button to get more details.
2. The project cleanup wizard starts. This wizard indicates the unused files that can be deleted.
3. Go to the next step.
4. Select the type of cleanup to perform. You can:
  - create a zip file with the useless files.
  - move the useless files into a specific directory.
5. Validate the option proposed by default and go to the next step.
6. Finish the wizard.

Our project was optimized according to the tips given by the static audit.

The static audit is used to get an overall status on the source code of your project. Our advice: run it on a regular basis!

Let's see what happens at run time by starting the dynamic audit.

Dynamic audit

The dynamic audit is used to study the application execution. The audit is used to detect problems such as:

Excessive memory consumption,
Slowness of algorithms used,
Errors "hidden" at runtime,
...

A dynamic audit can be performed in a test environment or on a live application.

The "WD Optimization" project contains a specific window triggering errors that can be detected by the dynamic audit.

The dynamic audit and the project test will be started at the same time.

To start the dynamic audit on the "WD Optimization" project:

On the "Project" pane, in the "Test mode" group, expand "Test mode" and select "Debug the project while the audit is enabled". The project test is run.


	Remark	The dynamic audit of the project can also be started from the project dashboard, via the "Execution" widget. To do so: enable the Widget if necessary (click the link "Click here to re-enable"). expand the arrow and select "Detailed Go of project". Remark: The dynamic audit is automatically run whenever the application is started by a project GO. A report is automatically displayed in the project dashboard:

Click the "Test window of dynamic audit" button.
Click the different buttons found in the window. At the end of each process, a toast message is displayed to specify that the process is over. For the "Assertion and Exception" option, an assertion is displayed: click "Continue" in order for the message to appear in toast format.
Stop the application test.
The report window of the dynamic audit appears.

Let's study this window:
- The top section of this window is used to choose the display mode of data. You can:
  - choose a chronological display (respecting the order in which the events occurred) or an overall display, used to group the different types of problems. In this case, the chronological border allows you to see the position and importance of problems.
  - choose the type of problem to display (error, assertion, ...). This allows you for example to concentrate on the major errors, ...
- The bottom section of this window displays the different events that occurred and that may cause problems in the application.

In this example, the dynamic audit detects several problems:
- An excessively long caption that is assigned by programming,
- A SWITCH loop for which no CASE is run,
- An assertion is triggered instead of an exception,
- The opening of a file that does not exist,
- The assignment of a nonexistent image file to an Image control.
For each problem, a "..." button is used to access the event details. If the event is linked to a specific line of code, the button allows you to open the code editor directly at the corresponding location in order to fix the problem.

Close the window of dynamic audit.


	Remark	The dynamic audit of a project can also be performed when an application is deployed on the user computers. You can: modify the application and use dbgEnableAudit to start the audit. use a text file in the application directory. This solution allows you not to modify the executable. Simply create a file in the same directory and with the same name as the executable, but with a ".WX" extension. The audit generates a ".wdaudit" file, this file must be loaded in the development environment in order to study the result. See Dynamic audit for more details.

Páginas

sexta-feira, 28 de agosto de 2020

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

https://youtu.be/w3HJ3X-PnSA

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

https://youtu.be/wdYlVdAzE5I

https://repository.windev.com/

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

https://youtu.be/jT504xmXnP0

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

https://youtu.be/Nihd09vTHeY

https://repository.windev.com/

https://youtu.be/3DshsXJ8I2M

https://youtu.be/EqnYJFpvPAI

Teste

Marcadores


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