Are Azure functions running in consumption mode suitable for bulk change but critical load time?
I'm about to start working on an API that will literally go from 0 RPS to a couple of hundred thousand HTTP RPS at the same time and run at that speed for ~ 2 minutes. All processing of these 30 million requests should be completed by the end of this 2-minute period. This will happen 7 times a week.
Moving to a serverless server with Azure Functions on a Consumption Plan. Hosting mode sounds attractive. This document describes that there is a scale controller for coordinating application instances, but does not really discuss what I can expect from it for HTTP triggers. I can't find any information that says the scale controller will be able to respond in the time frame I need.
The best information I could find was this information , which said it took about 8 minutes to test it.
Is this a bad use case for Azure Functions in consumption mode?
Obviously, unscrewing a test harness capable of issuing 30 million requests in 2 minutes is self-sufficient and costly. I would like to learn from others who have already done this.
source to share
Based on my experience, this scenario is not properly covered by the Consumption Plan. They can scale in many cases, but not very quickly. 2 minutes is too fast to rely on.
I mostly worked with queues, not HTTP, but I had delays of up to 40 minutes due to the slow scaling rate.
If you can predict which 2 minutes the heavy load will be, the best option might be to provide capacity with a script (or other function).
source to share