Skip to content

Commit a9a06f6

Browse files
Apply suggestions from code review
😇Glenn 😇 Co-Authored-By: Glenn Gailey <[email protected]>
1 parent 4aca319 commit a9a06f6

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/azure-functions/functions-bindings-warmup.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Azure Functions warmup trigger
33
description: Understand how to use the warmup trigger in Azure Functions.
4-
services: functions
54
documentationcenter: na
65
author: alexkarcher-msft
76
manager: gwallace
@@ -13,9 +12,9 @@ ms.date: 11/08/2019
1312
ms.author: alkarche
1413
---
1514

16-
# Azure Functions Warmup Trigger
15+
# Azure Functions warm-up trigger
1716

18-
This article explains how to work with the warmup trigger in Azure Functions. This trigger type allows your function app to pre-load custom dependencies during the [pre-warming process](./functions-premium-plan.md#pre-warmed-instances) when running in the [Premium plan](./functions-premium-plan.md). You can use a warmup trigger to ensure your functions have already loaded all of their dependencies when they start processing requests.
17+
This article explains how to work with the warmup trigger in Azure Functions. The warmup trigger is supported only for function apps running in a [Premium plan](functions-premium-plan.md). A warmup trigger is invoked when an instance is added to scale a running function app. You can use a warmup trigger to pre-load custom dependencies during the [pre-warming process](./functions-premium-plan.md#pre-warmed-instances) so that your functions are ready to start processing requests immediately.
1918

2019
[!INCLUDE [intro](../../includes/functions-bindings-intro.md)]
2120

@@ -31,7 +30,7 @@ The warmup trigger lets you define a function that will be run on an instance wh
3130

3231
The warmup trigger is intended to create shared dependencies that will be used by the other functions in your app. [See examples of shared dependencies here](./manage-connections.md#client-code-examples).
3332

34-
Not that the warmup trigger is only called during scale up operations, not during restarts or other non-scale startups. You must ensure your logic can load all necessary dependencies without using the warmup trigger. Lazy loading is a good pattern to achieve this.
33+
Not that the warmup trigger is only called during scale-up operations, not during restarts or other non-scale startups. You must ensure your logic can load all necessary dependencies without using the warmup trigger. Lazy loading is a good pattern to achieve this.
3534

3635
## Trigger - example
3736

@@ -41,7 +40,7 @@ The following example shows a [C# function](functions-dotnet-class-library.md) t
4140

4241

4342
* Your function must be named ```warmup``` and there may only be one warmup function per app.
44-
* To use warmup in dotnet functions, please make sure you have a package reference to **Microsoft.Azure.WebJobs.Extensions >= 3.0.5**
43+
* To use warmup as a .NET class library function, please make sure you have a package reference to **Microsoft.Azure.WebJobs.Extensions >= 3.0.5**
4544
* ```<PackageReference Include="Microsoft.Azure.WebJobs.Extensions" Version="3.0.5" />```
4645

4746

@@ -75,7 +74,7 @@ namespace WarmupSample
7574

7675
The following example shows a warmup trigger in a *function.json* file and a [C# script function](functions-reference-csharp.md) that will run on each new instance when it is added to your app.
7776

78-
Your function must be named ```warmup``` and there may only be one warmup function per app.
77+
Your function must be named ```warmup```, and there may only be one warmup function per app.
7978

8079
Here's the *function.json* file:
8180

0 commit comments

Comments
 (0)