1. Nerdio Manager for Enterprise
  2. Community
  3. NME Ecosystem

ARM API Limits?

Avatar
Ryan Skelly

"In practice, you probably need to add 1-2 extra app registrations to satisfy the API limits. For very large environments, you may need 3 or more extra apps registered" per this Nerdio KB article

To help ensure our Nerdio app is scaled appropriately, can staff or peers add any clarification/examples/prior experiences on what constitutes a very large deployment? At what point have others hit ARM API limits? Are there any additional costs incurred by adding additional app registrations?

Looking for some metrics and input to anticipate our need for these app boosters prior to them becoming an issue. Current usage is not very clear to us against the published limits.

Thanks in advance

2

Comments (1 comment)

Sort by
Avatar
Neil McLoughlin

Hi Ryan, 

The reason why it's not very clear is because it is very much dependent upon a number of different factors. For example, is the Subscription shared with non-AVD resources, single-session hosts, multi-session hosts, etc. From personal experience, you won't really start hitting any API Limits until you have at least 1000 VMs with autoscaling enabled. But then again, I have customers for whom we have tweaked the app settings and are hitting 5000 VMs per subscription with no problems. If you do hit API limits, we recommend you contact our support team, and we can work with you to optimise the environment. Still, we generally advise customers never to go above 2500 VMs per subscription, and then you should not hit any issues. We recently made changes to use the Graph API and that has massively helped with other customers. 

Are for the additional costs for App Registrations there are none.  

1

Please sign in to leave a comment.