question

RodolfoMacaraeg avatar image
0 Votes"
RodolfoMacaraeg asked RodolfoMacaraeg commented

What is the impact of increasing Azure Application Gateway Timeout?

Hi! I'm a newbie in supporting Azure services for a client. I would like to know if there is an impact in performance and pricing when increasing the Azure appgw timeout of our setup? Currently, we have a premium subscription and our gateway is configured with WAF V2 tier autoscale 0-10, and timeout is at default 20sec in prod (60s in staging). In the website, https://azure.microsoft.com/en-us/pricing/calculator/ , I can see that capacity unit (compute unit, connections, and throughput) are variables in computing monthly cost. Will this pricing computation be impacted by the change in timeout? How about the app gateway performance, and connection to APIM service?

The current average capacity of APIM is at 12% and maxing at 25%. While request is currently at around 200 per minute which is far from our current subscription 4000 per seconds.
130084-image.png


azure-application-gateway
image.png (102.7 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SaiKishor-MSFT avatar image
0 Votes"
SaiKishor-MSFT answered RodolfoMacaraeg commented

@RodolfoMacaraeg-5593 Thank you for reaching out to Microsoft Q&A.

For v2: Application Gateway Pricing | Microsoft Azure (at the bottom of the page) - capacity unit is determined by how much traffic the gateway is processing (throughput, persistent connections, and compute unit). changing the request timeout value should not affect the cost as it wouldn't affect any of the three things that contribute to cost. However, this may effect the performance as the connections remain open for longer. Hope this helps.

Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

Remember:

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

Want a reminder to come back and check responses? Here is how to subscribe to a notification.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you @SaiKishor-MSFT for your answer!

One more thing, currently, as per checking our logs, the max instance used by our gateway is 2 but we configured it to have 10 max instance.
Also, we only experience around 0-5 request timing out, out of 50K-80K transactions per day.

Does this still impact performance? and what do we actually consider when checking performance of gateway?

131824-image.png


0 Votes 0 ·
image.png (22.9 KiB)
learn2skills avatar image
0 Votes"
learn2skills answered RodolfoMacaraeg commented

Hi @RodolfoMacaraeg-5593

The Keep-Alive timeout in the Application Gateway v1 SKU is 120 seconds and in the v2 SKU it's 75 seconds. The TCP idle timeout is a 4-minute default on the frontend virtual IP (VIP) of both v1 and v2 SKU of Application Gateway.
already answered more details



If the Answer is helpful, please click Accept Answer and up-vote, so that it can help others in the community looking for help on similar topics.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @learn2skills ! Thank you for your feedback but I am pertaining to the timeout in HTTP setting which is defaulted to 20 seconds. Also, I wanted to know the impact on performance and financial especially with high volume of traffic coming in given that requests will not timeout at 20s but to a longer configuration.

0 Votes 0 ·