Table of Contents

Performance Profiler

General

In v25 Microsoft has introduced the Performance Profiler. With this functionality, a consultant and/or key-user can investigate whether a specific cause can be identified for performance problems.

For more information on the functionality see: Microsoft Learn

Example using Performance Profiler

A customer has experienced that when creating and posting invoices the execution takes longer than normal. The following steps have to be performed:

1. Prepare process

The normal business process has to be completed untill the moment invoices can be created.

2. Start Performance Profiler

  • Start the 3PL Dynamics web-client
  • Start the help menu by clicking on the help button: Question Mark
  • Select the option: Help & Support
  • Go to the paragraph: Troubleshooting and Select the option: Analyze Performance A new window will be opened on which the Performance Profiler can be started
  • Click on the action: Start to start the Performace Profiler. From now on all actions in the webclient will be monitored

3. Perform Business process

  • Return to the 3PL Dynamics web-client
  • Execute the normal business process of creating and posting invoices.

4. Stop Performance Profiler

  • Return to the window in which the Performance Profiler was started
  • Click on the action: Stop to end the Performance Profiler

5. Analyze usage per APP

The graphs on the tab: Performance Profiler and Time Spent shows the usage per APP, required to handle the process.

As the following example shows The Microsoft Base Application APP requires the most time.

Results1

Tip

Swith the button: Show technical information to: on to present the pie-graph.

6. Analyze detailed info

The Tab: Time spent by Application Object shows what time each object requires to perform the process. As this overview is sorted on Timme Spent the objects requiring the most time will be listed at the top, as shown in the expample below.

Results2

Tip

Click on the expand-button at the beginning of a row to see more details on the process.

7. Conclusion

The results show that the Posting of the invoice is causing the long duration. The business-process has been repeated once more with a simular order. As shown in the example below the Post-action now only required 1 second in stead of 19 seconds.

Results3

Conclusion is that the duration of the execution of the process varies a lot.An other process must be infuencing the process of posting the invoice at the specific date/time.

Other processes that may cause the delay in performance:

  • Is a colleque performing a job at the specific time, which requires a lot of performance?
  • Is a specific taks in the jobqueue running at the specific time.
  • Is an API running at the specific time. For example for an data-integration or Business Annalysis tool.
  • Is the latest application version of Business Central Dynamics running?
Edit this page