Skip to content

Commit b454955

Browse files
mrbullwinklemrbullwinkle
committed
Merge branch 'master' of https://github.com/jr-MS/azure-docs-pr into mrb_02_01_2023_ad
2 parents 0714184 + c8086e0 commit b454955

File tree

3 files changed

+99
-0
lines changed

3 files changed

+99
-0
lines changed

‎articles/cognitive-services/Anomaly-Detector/How-to/batch-inference.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ You could choose the batch inference API, or the streaming inference API for det
3030

3131
To perform batch inference, provide the blob URL containing the inference data, the start time, and end time. For inference data volume, at least `1 sliding window` length and at most **20000** timestamps.
3232

33+
To get better performance, we recommend you send out no more than 150,000 data points per batch inference. *(Data points = Number of variables * Number of timestamps)*
34+
3335
This inference is asynchronous, so the results aren't returned immediately. Notice that you need to save in a variable the link of the results in the **response header** which contains the `resultId`, so that you may know where to get the results afterwards.
3436

3537
Failures are usually caused by model issues or data issues. You can't perform inference if the model isn't ready or the data link is invalid. Make sure that the training data and inference data are consistent, meaning they should be **exactly** the same variables but with different timestamps. More variables, fewer variables, or inference with a different set of variables won't pass the data verification phase and errors will occur. Data verification is deferred so that you'll get error messages only when you query the results.

‎articles/cognitive-services/Anomaly-Detector/service-limits.md

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: Service limits - Anomaly Detector service
3+
titleSuffix: Azure Cognitive Services
4+
description: Service limits for Anomaly Detector service, including Univariate Anomaly Detection and Multivariate Anomaly Detection.
5+
services: cognitive-services
6+
author: jr-MS
7+
manager: nitinme
8+
ms.service: cognitive-services
9+
ms.subservice: anomaly-detector
10+
ms.topic: conceptual
11+
ms.date: 1/31/2023
12+
ms.author: jingruhan
13+
ms.custom:
14+
---
15+
16+
# Anomaly Detector service quotas and limits
17+
This article contains both a quick reference and detailed description of Azure Anomaly Detector service quotas and limits for all pricing tiers. It also contains some best practices to help avoid request throttling.
18+
19+
The quotas and limits apply to all the versions within Azure Anomaly Detector service.
20+
21+
## Univariate Anomaly Detection
22+
|Quota<sup>1</sup>|Free (F0)|Standard (S0)|
23+
|--|--|--|
24+
| **All APIs per second** | 10 | 500 |
25+
26+
<sup>1</sup> All the quota and limit are defined for one Anomaly Detector resource.
27+
28+
## Multivariate Anomaly Detection
29+
30+
### API call per minute
31+
|Quota<sup>1</sup>|Free (F0)<sup>2</sup>|Standard (S0)|
32+
|--|--|--|
33+
| **Training API per minute** | 1 | 20 |
34+
| **Get model API per minute** | 1 | 20 |
35+
| **Batch(async) inference API per minute** | 10 | 60 |
36+
| **Get inference results API per minute** | 10 | 60 |
37+
| **Last(sync) inference API per minute** | 10 | 60 |
38+
| **List model API per minute** | 1 | 20 |
39+
| **Delete model API per minute** | 1 | 20 |
40+
41+
<sup>1</sup> All quotas and limits are defined for one Anomaly Detector resource.
42+
43+
<sup>2</sup> For **Free (F0)** pricing tier see also monthly allowances at the [pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/anomaly-detector/)
44+
45+
46+
### Concurrent models and inference tasks
47+
|Quota<sup>1</sup>|Free (F0)|Standard (S0)|
48+
|--|--|--|
49+
| **Maximum models** *(created, running, ready, failed)*| 20 | 1000 |
50+
| **Maximum running models** *(created, running)* | 1 | 20 |
51+
| **Maximum running inference** *(created, running)* | 10 | 60 |
52+
53+
<sup>1</sup> All quotas and limits are defined for one Anomaly Detector resource. If you want to increase the limit, please contact [email protected] for further communication.
54+
55+
56+
## How to increase the limit for your resource?
57+
For the Standard pricing tier, this limit can be increased. Increasing the **concurrent request limit** does not directly affect your costs. Anomaly Detector service uses "Pay only for what you use" model. The limit defines how high the Service may scale before it starts throttle your requests.
58+
59+
The **concurrent request limit parameter** is not visible via Azure portal, Command-Line tools, or API requests. To verify the current value, create an Azure Support Request.
60+
61+
If you would like to increase your limit, you can enable auto scaling on your resource. Follow this document to enable auto scaling on your resource [enable auto scaling](https://learn.microsoft.com/azure/cognitive-services/autoscale?view=form-recog-3.0.0&tabs=portal). You can also submit an increase Transactions Per Second (TPS) support request.
62+
63+
### Have the required information ready
64+
65+
* Anomaly Detector Resource ID
66+
67+
* Region
68+
69+
#### How to get those information above:
70+
71+
* Go to [Azure portal](https://portal.azure.com/)
72+
* Select the Anomaly Detector Resource for which you would like to increase the transaction limit
73+
* Select Properties (Resource Management group)
74+
* Copy and save the values of the following fields:
75+
* Resource ID
76+
* Location (your endpoint Region)
77+
78+
79+
### Create and submit support request
80+
Initiate the increase of limit for your resource by submitting the Support Request:
81+
82+
* Go to [Azure portal](https://portal.azure.com/)
83+
* Select the Anomaly Detector Resource for which you would like to increase the limit
84+
* Select New support request (Support + troubleshooting group)
85+
* A new window will appear with auto-populated information about your Azure Subscription and Azure Resource
86+
5. Enter Summary (like "Increase Anomaly Detector TPS limit")
87+
6. In Problem type, select *"Quota or usage validation"*
88+
7. Select Next: Solutions
89+
8. Proceed further with the request creation
90+
9. Under the Details tab enters the following in the Description field:
91+
* A note, that the request is about Anomaly Detector quota.
92+
* Provide a TPS expectation you would like to scale to meet.
93+
* Azure resource information you collected.
94+
* Complete entering the required information and select Create button in *Review + create* tab
95+
* Note the support request number in Azure portal notifications. You'll be contacted shortly for further processing

‎articles/cognitive-services/Anomaly-Detector/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99
href: https://aka.ms/adpricing
1010
- name: What's new
1111
href: whats-new.md
12+
- name: Service limits
13+
href: service-limits.md
1214
- name: FAQ
1315
href: faq.yml
1416
- name: Quickstarts

0 commit comments

Comments
 (0)