Performance profiling
With or without a snapshot debugger log, the Dynamics 365 Business Central service can be instructed to collect an AL code performance profiler trace.
As with snapshot debugging, profiling is tightly related to the request parameter, which must be set to snapshotinitialize, and overall, by the executionContext property specified in the launch.json file. This last one can be configured to collect only an AL Profiler trace or both snapshot and profiler traces (DebugAndProfiler).
Another important parameter that influences the frequency of value collection within a given time is the "profilingType" parameter specified in the launch.json file. Profiling can be of two different types:
- Instrumentation, where any AL procedure is wrapped in telemetry instrumentational code that captures time measures.
- Sampling, where measures are collected only within very specific and constant sampling intervals through a separate collection process...
