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.
Daniel Grenemark commented
This about sums it up: https://imgflip.com/i/27qhxe
Here is another request with Planned status on Feb 22, 2018: https://feedback.azure.com/forums/217313-networking/suggestions/19580290-reduce-update-times-for-application-gateways
Please keep us updated on performance improvements to Application Gateway. Thank you
This is unusable. I've deployed loads of stuff to azure, but this... I get a 502 error, which I'd try to debug but it takes soooooo long to make simple changes it's just too painful. Giving up on this.
Omg, I thought I did something wrong until I saw this and knew it's you did something wrong.
this is such a core feature but you guys support it so badly. Unbelievable.
piece of sh*t
Please fix this, the application gateway is unacceptably slow to manage
I have to agree with everybody else. Updating the configuration on the Application Gateway is Unacceptably slow, to the point the service is unusable.
Please fix, i cant recommend this product when basic things takes forever to change, if you have and error its a pain to debug as simple changes takes forever.
Mehmet Kut commented
Please improve this as soon as possible.
It is just Appllication Gateway not a Falcon Heavy right?
Azure services have to fast!
In Turkish we say that "Ömür törpüsü."
Paul Spurrell commented
So slow its painful to use
This is horrendous performance, especially considering that changes are single threaded. I could overlook this if I could go through and make several changes at once when setting up a new WAF, but making a config change while still waiting on the first change cancels the first one. Ugh.
Doug Brand-Williamson commented
This is really frustrating - simple operations take forever to take affect and often timeout completely.
Will this be fix some day
Not to mention...I think they made the app gateway slower than the WAF feature was in public preview. It used to take 5-10 min for every change, which was bad... Now, I'm waiting over an hour and 15 min for one cert change... It boggles my mind completely.
Vivek V commented
I'd say this is the horrible product I've used from Azure. Deploying an Application Gateway takes around 30 minutes and each change takes around 45 minutes. Configuring a simple domain requires at least 4-5 steps and it is a nightmare to get this done.
I hit the submit button and goto kitchen, make a coffee and sandwich, watch an episode of TV show and come back and watch a music video on youtube and finally my first change is done.
I wonder when Microsoft is going to fix this performance issue.
Nicholas Piasecki commented
I was researching this product to enable a rolling deployment scenario, assuming I could temporarily drop machines out of a pool like in ARR. In fact I just assumed it would be ARR under the hood. Who implements a product that takes 15 minutes to add a single rule and says "yes, looks fine"?
It does take an exceptionally long time to apply changes.
What is worse is that where you have to make several changes, each change is applied separately, meaning configuring a new service can take a significant amount of time as you wait for each separate change to be applied.
And when you do finally get the change applied, you frequently end up with 502 errors without any indication as to which of the multiple error types caused the issue.