You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-limits-quotas-capacity.md
+8-32Lines changed: 8 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ author: HeidiSteen
8
8
ms.author: heidist
9
9
ms.service: cognitive-search
10
10
ms.topic: conceptual
11
-
ms.date: 09/04/2024
11
+
ms.date: 09/19/2024
12
12
ms.custom:
13
13
- references_regions
14
14
- build-2024
@@ -80,53 +80,29 @@ When estimating document size, remember to consider only those fields that add v
80
80
81
81
When you index documents with vector fields, Azure AI Search constructs internal vector indexes using the algorithm parameters you provide. The size of these vector indexes is restricted by the memory reserved for vector search for your service's tier (or `SKU`).
82
82
83
-
The service enforces a vector index size quota **for every partition** in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
84
-
85
-
Vector limits vary by service creation date and tier.
86
-
87
-
+ To check the age of your search service or learn more about vector indexes, see [Vector index size and staying under limits](vector-search-index-size.md).
88
-
89
-
+ To view the vector quota in effect for your search service, use [GET Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics), or check the **Properties** and **Usage** tabs for your search service in the Azure portal.
90
-
91
-
#### Vector quota per partition (GB)
83
+
Vector limits vary by [service creation date](vector-search-index-size.md#how-to-check-service-creation-date) and [tier](search-sku-tier.md). For guidance on managing and maximizing vector storage, see [Vector index size and staying under limits](vector-search-index-size.md).
92
84
93
85
This table shows the progression of vector quota increases in GB over time. The quota is per partition, so if you scale a new Standard (S1) service to 6 partitions, total vector quota is 35 multiplied by 6.
94
86
95
87
| Service creation date |Basic | S1| S2 | S3/HD | L1 | L2 |
<sup>1</sup> Initial vector limits during early preview.
103
95
104
96
<sup>2</sup> Vector limits during the later preview period. Three regions didn't have the higher limits: Germany West Central, West India, Qatar Central.
105
97
106
-
<sup>3</sup> Higher vector quota based on the larger partitions for supported tiers and regions.
98
+
<sup>3</sup> Higher vector quota based on the larger partitions for supported tiers and regions.
107
99
108
100
<sup>4</sup> Higher vector quota for more tiers and regions based on partition size updates.
109
101
110
-
#### Partition limits (GB)
111
-
112
-
This table repeats [partition storage limits](#service-limits) for context. The table shows the progression of storage quota increases in GB over time. Vector quota is per partition, so the more significant increases in vector quota that occurred starting in April 2024 correspond to the increases in per-partition storage occuring at the same time.
113
-
114
-
Higher capacity partitions were brought online starting in April 2024.
115
-
116
-
| Service creation date |Basic | S1| S2 | S3/HD | L1 | L2 |
<sup>1</sup> Partition sizes during early preview.
124
-
125
-
<sup>2</sup> No change during the later preview period.
126
-
127
-
<sup>3</sup> Higher capacity storage for Basic, S1, S2, S3 in these regions. **Americas**: Brazil South, Canada Central, Canada East, East US, East US 2, Central US, North Central US, South Central US, West US, West US 2, West US 3, West Central US. **Europe**: France Central. Italy North, North Europe, Norway East, Poland Central, Switzerland North, Sweden Central, UK South, UK West. **Middle East**: UAE North. **Africa**: South Africa North. **Asia Pacific**: Australia East, Australia Southeast, Central India, Jio India West, East Asia, Southeast Asia, Japan East, Japan West, Korea Central, Korea South.
102
+
The service enforces a vector index size quota **for every partition** in your search service. Each extra partition increases the available vector index size quota. This quota is a hard limit to ensure your service remains healthy, which means that further indexing attempts once the limit is exceeded results in failure. You can resume indexing once you free up available quota by either deleting some vector documents or by scaling up in partitions.
128
103
129
-
<sup>4</sup> Higher capacity storage for more tiers and more regions. **Europe**: Germany North, Germany West Central, Switzerland West. **Azure Government**: Texas, Arizona, Virginia. **Africa**: South Africa North. **Asia Pacific**: China North 3, China East 3.
104
+
> [!IMPORTANT]
105
+
> Higher vector limits are tied to larger partition sizes. Regions that run on older infrastructure are subject to the July-April limits. Review the [regions list](search-region-support.md) for status on partition storage limits.
0 commit comments