Performance profiling

Together or separated from a snapshot debugger log, it is also possible to instruct the Dynamics 365 Business Central service to collect an AL code performance profiler trace. This is tightly related to the "executionContext" parameter specified in the launch.json file. This could be configured to collect only an AL "Profile" trace or both snapshot and profile traces ("DebugAndProfile"). Another important parameter, that influence the frequency of collecting values within a given time, is the "profilingType" parameter specified in the launch.json file. Profiling could be of 2 different types:

• "Instrumentation" where any AL procedure is wrapped before and after by telemetry instrumentational code that would capture time measures in the most analytic way.
• "Sampling" where measures are collected only within very specific and constant sampling intervals through a separate collection process.

Since with Dynamics...