Query on Azure Functions Elastic Premium Plan Scaling Behavior

Janice Chi 140 Reputation points
2025-05-15T09:14:00.26+00:00

Query on Azure Functions Elastic Premium Plan Scaling Behavior

We are testing high-throughput ingestion from Kafka using Azure Functions (Premium Plan). Our expected event rate is 68,400 EPS. We want to confirm the actual instance warm-up rate and how many messages per second one EP1, EP2, or EP3 instance can handle without hitting CPU/memory bottlenecks.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,925 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Ranashekar Guda 2,825 Reputation points Microsoft External Staff Moderator
    2025-05-15T23:11:19.07+00:00

    Hello @Janice Chi,
    To determine the scaling behavior of Azure Functions on the Premium Plan for high-throughput ingestion from Kafka, we need to consider the scaling capabilities of the plan. Here is the information you need:

    1. Azure Functions Premium Plan Scaling:
    • The Premium Plan scales out automatically based on the number of events that trigger its functions.
    • The maximum number of instances for the Premium Plan varies based on the operating system:
    • Windows: 100 instances & Linux: 20-100 instances
    1. Instance Warm-up Rate:
    • The warm-up rate of instances in the Premium Plan depends on the incoming trigger events and the scaling behavior of the plan.
    • As the plan scales out automatically, new instances are added to handle the increased load, ensuring that the functions can process the incoming events efficiently.
    1. Messages Per Second Handling:
    • The number of messages per second that an instance can handle without hitting CPU/memory bottlenecks can vary based on the complexity of your functions, the resources allocated to each instance, and the processing requirements of your Kafka ingestion.
    • It's recommended to perform load testing with your specific workload to determine the optimal message processing rate per instance.

    Considering the expected event rate of 68,400 EPS, you may need to distribute the load across multiple instances within the Premium Plan to ensure efficient processing without hitting bottlenecks.
    Kindly refer below links:
    https://techcommunity.microsoft.com/blog/fasttrackforazureblog/azure-functions---part-1---hosting-and-networking-options/3746795
    https://learn.microsoft.com/en-us/azure/azure-functions/functions-premium-plan?tabs=portal

    https://learn.microsoft.com/en-us/azure/azure-functions/event-driven-scaling?tabs=azure-cli
    Hope this helps. Do let us know if you any further queries.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.