![]() 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 |