You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-warmup.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
---
2
2
title: Azure Functions warmup trigger
3
3
description: Understand how to use the warmup trigger in Azure Functions.
4
-
services: functions
5
4
documentationcenter: na
6
5
author: alexkarcher-msft
7
6
manager: gwallace
@@ -13,9 +12,9 @@ ms.date: 11/08/2019
13
12
ms.author: alkarche
14
13
---
15
14
16
-
# Azure Functions Warmup Trigger
15
+
# Azure Functions warm-up trigger
17
16
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.
@@ -31,7 +30,7 @@ The warmup trigger lets you define a function that will be run on an instance wh
31
30
32
31
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).
33
32
34
-
Not that the warmup trigger is only called during scaleup 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.
35
34
36
35
## Trigger - example
37
36
@@ -41,7 +40,7 @@ The following example shows a [C# function](functions-dotnet-class-library.md) t
41
40
42
41
43
42
* 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**
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.
77
76
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.
0 commit comments