Azure-docs: Add limits on TCP connections per instance in doc and portal

Created on 22 May 2019  Â·  32Comments  Â·  Source: MicrosoftDocs/azure-docs

In practice, we noticed that our web app has lit the limitation on TCP connections per instance, for example, I was told by some one that maximum connection limits are 1,920 connections per B1/S1/P1 instance, 3,968 connections per B2/S2/P2 instance, 8,064 connections per B3/S3/P3 instance.

However, this information is not recorded in your official docs on pricing tiers (https://azure.microsoft.com/en-us/pricing/details/app-service/windows/) nor azure portal when we choose the instance type for our web app.

Per my understanding, this is quite misleading and confusing when we choose different pricing tiers. My current project is impacted by this greatly when it has additional CPU/memory, etc resources while lacking tcp connections.

I do wish you can add detailed information about limitations when I need to make decisions like this. A link in portal scale-up could be much better.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri1 assigned-to-author billinsvc doc-enhancement triaged

Most helpful comment

@linruhui Thank you for your consistency in this issue. It took a while for us to track down the right party. I've added the information into the service limits doc now and it should be published sometime today. Sorry for the delay.

please-close

All 32 comments

@linruhui Thanks for the feedback! We are currently investigating and will update you shortly.

@rothja Could you please review this request and update as needed?

@linruhui Thank you for this feedback, and I am sorry you ran into this limitation without seeing it documented anywhere. I manage this article, but I need to pull in an app-service expert.

@SadiqhAhmed-MSFT , could you please assign this to @cephalin to triage and then unassign me from this issue. I think Cephas is the right person to work on it or to find the right person to help. Thank you!

@rothja Thanks for the reply. Assigned to @cephalin as suggested.

@cephalin What's the latest status on this problem? Is there any conclusion that you can share?

@cephalin @SadiqhAhmed-MSFT Can you please push this thread a little forward? 11 days has passed and we still get no response.

@linruhui So sorry for the delay. I'm going to try to look into this as well and see where we are at. Thank you!

@rothja Thank you for following up. I understand it will be much complicated and time consuming to add this information in the document. Is it possible that you share the temporary conclusion with me? Will this limitations be added in official document?

hello guys, any update on this thread?

@linruhui Sorry, again. I just spoke with @cephalin, and we are still trying to track down the right answer, but we appreciate the ping. We'll try to provide an update soon. Thank you for your patience.

@rothja Hope you are doing well. Is there any progress that you would like to share with us? Thanks.

Can anyone share current progress or any conclusions on this thread? Two months have passed and we still get no conclusion yet.

@linruhui Sorry still tracking down the numbers for free and shared tiers. However you can see the numbers for the other tiers at https://msdn.microsoft.com/en-us/magazine/mt793270.aspx (Look up "Network Port Capacity for Outbound Network Calls") which match the numbers you quoted.

Thank you @cephalin for the reply.
Do you have any plan to add these limitation of TCP connections in https://azure.microsoft.com/en-us/pricing/details/app-service/windows/ or azure portal when we choose the instance type for our web app?

@cephalin
Do you have any plan to add these limitation of TCP connections in https://azure.microsoft.com/en-us/pricing/details/app-service/windows/ or azure portal when we choose the instance type for our web app?

Because, if you choose azure Iaas, it is easy to link the different limitations of TCP connections to different virtual machine type. But when it goes to Azure Paas, users may not know clearly how many TCP connections he/she can use especially in cases like several apps hosted in one app service plan.

Can anyone help answer this question?

Do we have any plan to add these limitation of TCP connections in https://azure.microsoft.com/en-us/pricing/details/app-service/windows/ or azure portal when we choose the pricing tier for app service plan?

Can anyone help answer this question?

Do we have any plan to add these limitation of TCP connections in https://azure.microsoft.com/en-us/pricing/details/app-service/windows/ or azure portal when we choose the pricing tier for app service plan?

@linruhui Sorry for the delay. We're still tracking down the numbers for free and shared tiers. When we have all the numbers then we can publish them.

@cephalin Thank you for the reply. Glad to see it is still under process. These information is quite crucial for developers, hope it could be finished soon.

@cephalin May I know what's the current status on the data collecting?

@cephalin May I know when will you have these numbers published?

@cephalin @rothja can you at least response something?..

@rafek1241 Unfortunately I still haven't received a response regarding the Free and Shared numbers, so we can't publish the changes yet. But the numbers that @linruhui found for Basic/Standard/Premium/ASE are right.

@cephalin I really want you people to help get this work out soon, you are experts in this area, aren't you? I just don't understand why it takes so long to collect data. We recently met a new issue in TCP connections -- SNAT port exhaustion. Again, we don't get clear documents in Azure Paas on this topic.

Since you are taking soooooo long to collect data, do you mind to get more details on SNAT port in Azure Paas as well?

Can anybody share the latest status on this topic?

Can anybody share the latest status on this topic?

Can anybody share the latest status on this topic?

Are we going anywhere nearer the destination? Or we are not taking any actions?

@linruhui Thank you for your consistency in this issue. It took a while for us to track down the right party. I've added the information into the service limits doc now and it should be published sometime today. Sorry for the delay.

please-close

Is it published now? I didn't get it from https://azure.microsoft.com/pricing/details/data-transfers/

@linruhui Hello. I believe the changes that were made were to update the official Azure Limits article here: https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#app-service-limits. Do you see the changes on that page now? Thanks!

@rothja Thanks for the information. This thread is all good for closure.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bdcoder2 picture bdcoder2  Â·  3Comments

jharbieh picture jharbieh  Â·  3Comments

paulmarshall picture paulmarshall  Â·  3Comments

bityob picture bityob  Â·  3Comments

monteledwards picture monteledwards  Â·  3Comments