topic hubPlatform, DevOps & Performanceofficial - Microsoftreviewed - checked by Opus

Performance

Performance best practices for Business Central development: how to troubleshoot a performance problem (measure, locate the bottleneck, eliminate it) and which diagnostic tools to use, plus performance guidance for AL developers on pages, web services, reports, AL code, data access and testing.

Path: Development > Rules, guidelines, and best practices > Best practices > Performance · tier official · system platform · narrative reviewed (checked by Opus)

Overview

This section is about finding and fixing performance problems in Business Central and about writing AL code that performs well from the start. It has two pages and no subtopics.

“How to work with a performance problem” describes the troubleshooting process: measure, locate the bottleneck, eliminate it. It also lists the diagnostic tools: the scheduled performance profiler, the in-client Performance Profiler, the AL Profiler, telemetry with Azure Application Insights, database missing indexes and database wait statistics.

“Performance Articles for AL Developers” collects guidance for developers on efficient page design, web services, reports, AL coding patterns, data access optimization and testing. Start with the troubleshooting page when you have a slow scenario to analyze. Use the AL developer articles when designing or reviewing code.

Key points

  • The recommended approach to a performance problem is to measure, locate the bottleneck, then eliminate it.
  • Profiling tools covered: scheduled performance profiler, in-client Performance Profiler and AL Profiler.
  • Telemetry with Azure Application Insights is one of the diagnostic sources.
  • Database-level analysis uses Database Missing Indexes and Database Wait Statistics.
  • AL developer guidance covers page background tasks, Edit-in-Excel performance, query object optimization and partial records.
  • Developers can also find guidance on table extension impact analysis and event subscription performance.
  • The AL developer articles reference 2021 release wave 2, 2023 release wave 1 and 2023 release wave 2.
  • Topics span pages, web services, reports, AL coding patterns, data access and testing strategies.

Learn pages

Videos, posts and code changes

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 2 Learn pages