Is there some guidelines for maximum number of concurrent connections to a private link service that can be handled before resource get congested?

Question

We have a private link service in front of a load balancer with two VMs in the backend pool. Is there some guidelines for maximum number of concurrent connections to a private link service that can be handled before resource get congested?

Answer 1

@Andersen, Helge ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know the maximum number of concurrent connections that a Private Link Service(PLS) can support.

AFAIK, This is dependent on the service that is exposed via the PLS.

However, I shall check internally once again if there are any limits on Private Link Service concurrent connections and let you know

• In your case, this is the Load Balancer.
• While Load Balancer has a very high limit (the limit is not publicly available), it is designed to handle the maximum capacity of the backend pools.
• The bottleneck actually arrives at the number of concurrent requests your backend can handle.
• NOTE : LB only load balances the connection, the backend VMs should be capable of accepting the connections if it grows in large number.
• Now, for a individual VM , you can find the limits on Flow limits and active connections recommendations

VMs that belong to a virtual network can handle 500k active connections for all VM sizes with 500k active flows in each direction.

Cheers,

Kapil.