Application Gateway management operations are agonizingly slow
[Originally posted to Azure Portal forum - however should have been submitted here]
Most creates and updates for application gateway configuration (back-end pools, rules, listeners, certificates, etc.) take 5-10 minutes to apply. This is not a portal issue as it takes just as long via the API / CLI. (This is with even a single instance App Gateway)
Applying these same settings on Windows Server ARR directly takes only a minute or less, so I'm not sure where the performance issue lies, but there is tremendous room for improvement.
As it is currently, it provides waaaay too much time while waiting to consider the porting costs of a migration to the alternate cloud platform.
Update operations have been enhanced with fast update. The operations which continue to be slow are SSL Policy, SSL certificate, ports and scaling up/down. Most other operations like listener, rules, http settings, backend pool, backend pool members, probes should be of the order of ~1min now.
I recently started to work with Azure Application Gateway. First when I started changes were applied quite fast below 5 mins. Now as I am implementing more HTTP Settings and Rules, I noticed that chances can take more than an hour. For an agile working this is not acceptable.
Sean S. commented
I am not sure I agree with the completed state of this. The operations which continue to be slow are SSL Policy, SSL certificate, ports and scaling up/down. This is a horrible user experience. I have seen these take 30+ minutes to complete
Joost Groot commented
SSL uploading is still very slow. Wouldn't be such a problem, but when you are "adding" Listeners and just added a new HTTPS listener with new SSL, you can't add any other listener (http or https) from the portal. Even though it's a backend process.
Untill the SSL is added the error message keeps popping up when adding a simple http listener:
Failed to save application gateway changes
Failed to save configuration changes to application gateway '<appgateway>'. Error: Data must be specified for Certificate VNG-events/providers/Microsoft.Network/applicationGateways/<appgateway>/sslCertificates/<sslname>><appgateway>/<sslname>.'
I hope this will be fixed soon, cause I need to add 50 hostnames to a specific app.gateway and adding one wil take almost 15min, so you do the math :-)
Painful to work with and debug each change takes 15++ :-( please fix
Mahesh Arban commented
As of now It's same behavior we can see, its very slow and taken longer time to update any action which we perform on gateway!
App Gateway is still very slow :( Even worst with the AzureRM powershell scripts. Takes like 10 min to update application gateway. This slows down our CD process.
An impressive share! I have just forwarded this onto a coworker who had been doing a little
homework on this. And he actually ordered me dinner simply because
I found it for him… lol. So allow me to reword this….
Thank YOU for the meal!! But yeah, thanks for spending some time to discuss
this topic here on your blog.
regards: < href="https://www.techlazy.com/live-tv-streaming-sites/">EvehUNT1122</a>
Mikael Chudinov commented
App Gateway is still very slow. Changing HTTP settings configuration is extremely slow. It takes ~15 minutes.
The APPGW is terrible very very very slowly to apply rules, not scaling, applying rules, please correct this.
I always prefer AWS load balancers instead of azure services whenver applicable, Azure chnages are really extremely slow in most of the tasks, even a Linux VM start process is too much slow in Azure in comparison to AWS. Microsoft really need to make processes fast in agile working era.
Brian Ward commented
If you are experiencing issues, please post comments and update the new post below as this idea has been marked as resolved.
ZARRAI Oussema commented
We're challenging multiple WAF solutions. This slowness is clearly a show stopper !
Simon Lerpiniere commented
This is still horribly slow. Most updates (even the ones mentioned) take ~6mins+
Please can you resolve the speed of Application Gateway configuration. It is so dreadfully slow!
Dan Carpenter commented
Still unbelievably slow with operations to update rules, listeners, and other settings from the CLI.
Tim Smith commented
How is this marked completed? Every operation still takes around 5 minutes to apply...at least let us make a bunch of changes at the same time.
Yup wont recommend this , Cant believe this is happening in 2019
Srini Darapaneni commented
AGW is very slow in saving the configuration both from GUI and CLI ...Every save takes 20 to 30 mins
even hours.. unusable for mission-critical apps!
Chris Burns commented
I have birthdays in between API calls to update this service. It really needs to be faster.