When enabled for serverless jobs or pipelines, workloads start up and complete faster. Disabled, they fall back to standard performance mode, cheaper in DBUs but usually starting four to six minutes later than the trigger.
Also called performance mode.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Performance optimized in context, with comparison tables and the common traps.
Terms in this definition
- Serverless
Compute tier for single Azure SQL databases that scales automatically, pauses when idle and charges by the second. It is offered in General Purpose and Hyperscale, not Business Critical, and reserved capacity does not apply.
- Deployment modes
The two ways ARM can deploy: Incremental, the default, creates or updates what the template lists and ignores everything else; Complete also removes resource group contents absent from the template.
- DISABLED
A plan mode that still allows editing, testing and scanning, but turns off scheduled runs and automatic report refreshes.
- Standard performance mode
With
performance_target: STANDARD, a serverless job consumes less compute and fewer DBUs, on the SKU that Performance optimized also uses, but takes 4 to 6 minutes to start. - Azure Functions trigger
Every function is started by exactly one thing. That thing might be a web call over HTTP, a schedule, the arrival of a blob, a message landing in a queue or a change in a database.