Home > other >  Azure Function workers vs instances
Azure Function workers vs instances

Time:04-14

I'm currently using an Azure Premium Service App (P3v3). I found that my function needs some boost, so I decided to look at how I can configure scaling. I found two available options:

  1. Set FUNCTIONS_WORKER_PROCESS_COUNT in the configuration section
  2. Configure the number of instances in Scale-Out menu

But what is the difference between instances and workers? Haven't found any information about that or how it can affect costs.

CodePudding user response:

what is the difference between instances (Scale-Out menu) and workers (FUNCTIONS_WORKER_PROCESS_COUNT)?

These are Microsoft Documentations to understand Workers and Instances in terms of Cost Management (Billing) and Functionality:

MSFT Sources of FUNCTIONS_WORKER_PROCESS_COUNT:

  1. P3v3PricingCalculator

    When it comes to Cost Management, the incremental nature of the Scale-Out methodology is extremely beneficial.

    Cost increases should be somewhat predictable because the components are identical.

    Scaling out also allows you to respond more quickly to changes in demand.

    In most cases, services can be quickly added or deleted to satisfy resource requirements. By just using (and paying for) the resources required at the time, this flexibility and speed effectively minimize spending.

    Refer to this article for more information on cost management and the benefits of Scale-Up and Scale-out.

  • Related