Triggers and bindings: The time taken to read input from and write output to your function bindings is counted as execution time. The following behaviors of your functions can impact the execution time: To learn more, see Bandwidth pricing details. However, you can incur costs for outbound data transfers to another region or outside of Azure. You don't pay for data transfer between Azure services in the same region. To learn more, see the Azure Monitor pricing page. A free grant of telemetry data is included every month. While not required, you should enable Application Insights integration. To learn more, see Storage account requirements.įunctions relies on Application Insights to provide a high-performance monitoring experience for your function apps. If you don't have a storage account, one is created for you when the function app is created. This account is used internally by the Functions runtime, but you can also use it for Storage triggers and bindings. Related costĮach function app requires that you have an associated General Purpose Azure Storage account, which is billed separately. When estimating the overall costs of your function app and related services, use the Azure pricing calculator. When calculating pricing for function apps, any triggers and bindings you have that integrate with other Azure services require you to create and pay for those additional services.įor functions running in a Consumption plan, the total cost is the execution cost of your functions, plus the cost of bandwidth and additional services. When estimating the overall cost of running your functions in any plan, remember that the Functions runtime uses several other Azure services, which are each billed separately. A 5xx response generated by the platform after your function code has started to execute is still counted as an execution, even if the error isn't raised by your function code. Similarly, 5xx status code responses aren't counted when they occur in the platform prior to a function processing the request. This means that 401 responses from the platform due to API key validation or the App Service Authentication / Authorization feature don't count against your execution cost. While CPU usage isn't directly considered in execution cost, it can have an impact on the cost when it affects the execution time of the function.įor an HTTP-triggered function, when an error occurs before your function code begins to execute you aren't charged for an execution. The calculation takes into account concurrency, which is multiple concurrent function executions in the same process. When your process is using 160 MB, you're charged for 256 MB. As mentioned on the pricing page, memory usage is rounded up to the nearest 128-MB bucket. The system does this calculation by sampling the memory usage of the process (along with child processes) at regular intervals. Since memory usage changes over time, the calculation is essentially the integral of memory usage over time. Then the execution cost is 0.5GB * 3s = 1.5 GB-seconds. For example, say that your function consumed 0.5 GB for 3 seconds. In this case, calculating the cost is simple multiplication. A function that runs for longer costs more, as does a function that consumes more memory.Ĭonsider a case where the amount of memory used by the function stays constant. Execution cost is calculated by combining its memory usage with its execution time. The execution cost of a single function execution is measured in GB-seconds. To learn more about the cost considerations when using Durable Functions, see Durable Functions billing. This article supersedes the Consumption plan cost billing FAQ article.ĭurable Functions can also run in a Consumption plan. This article deals only with the Consumption plan, since this plan results in variable costs. To learn more, see Azure Functions scale and hosting. You chose the plan that best supports your function performance and cost requirements. Cost is based on your chosen pricing tier. When you need to run in dedicated VMs or in isolation, use custom images, or want to use your excess App Service plan capacity. To learn more, see Azure Functions Premium plan.ĭedicated (App Service) (basic tier or higher) Provides you with the same features and scaling mechanism as the Consumption plan, but with enhanced performance and VNET access. This plan includes a free grant on a per subscription basis. You're only charged for the time that your function app runs. There are currently three types of hosting plans for an app that runs in Azure Functions, with each plan having its own pricing model: Plan
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |