Skip to content

Commit 0a86683

Browse files
authored
Merge pull request #207407 from gmndrg/main
Clarification of indexer max run time
2 parents 47053e7 + df2a484 commit 0a86683

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/search/search-limits-quotas-capacity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: HeidiSteen
88
ms.author: heidist
99
ms.service: cognitive-search
1010
ms.topic: conceptual
11-
ms.date: 06/10/2022
11+
ms.date: 08/09/2022
1212
---
1313

1414
# Service limits in Azure Cognitive Search
@@ -78,7 +78,7 @@ Maximum running times exist to provide balance and stability to the service as a
7878
| Maximum skillsets <sup>4</sup> |3 |5 or 15 |50 |200 |200 |N/A |10 |10 |
7979
| Maximum indexing load per invocation |10,000 documents |Limited only by maximum documents |Limited only by maximum documents |Limited only by maximum documents |Limited only by maximum documents |N/A |No limit |No limit |
8080
| Minimum schedule | 5 minutes |5 minutes |5 minutes |5 minutes |5 minutes |5 minutes |5 minutes | 5 minutes |
81-
| Maximum running time <sup>6</sup>| 1-3 minutes |2-24 hours |2-24 hours |2-24 hours |2-24 hours |N/A |2-24 hours |2-24 hours |
81+
| Maximum running time <sup>6</sup>| 1-3 minutes |2 or 24 hours |2 or 24 hours |2 or 24 hours |2 or 24 hours |N/A |2 or 24 hours |2 or 24 hours |
8282
| Maximum running time for indexers with a skillset <sup>5</sup> | 3-10 minutes |2 hours |2 hours |2 hours |2 hours |N/A |2 hours |2 hours |
8383
| Blob indexer: maximum blob size, MB |16 |16 |128 |256 |256 |N/A |256 |256 |
8484
| Blob indexer: maximum characters of content extracted from a blob |32,000 |64,000 |4&nbsp;million |8&nbsp;million |16&nbsp;million |N/A |4&nbsp;million |4&nbsp;million |
@@ -93,7 +93,7 @@ Maximum running times exist to provide balance and stability to the service as a
9393

9494
<sup>5</sup> AI enrichment and image analysis are computationally intensive and consume disproportionate amounts of available processing power. Running time for these workloads has been shortened to give other jobs in the queue more opportunity to run.
9595

96-
<sup>6</sup> Indexer maximum run time for Basic tier or higher may vary between 2 and 24 hours, depending on system resources, product implementation and other factors.
96+
<sup>6</sup> Indexer maximum run time for Basic tier or higher can be 2 or 24 hours, depending on system resources, product implementation and other factors.
9797

9898
> [!NOTE]
9999
> As stated in the [Index limits](#index-limits), indexers will also enforce the upper limit of 3000 elements across all complex collections per document starting with the latest GA API version that supports complex types (`2019-05-06`) onwards. This means that if you've created your indexer with a prior API version, you will not be subject to this limit. To preserve maximum compatibility, an indexer that was created with a prior API version and then updated with an API version `2019-05-06` or later, will still be **excluded** from the limits. Customers should be aware of the adverse impact of having very large complex collections (as stated previously) and we highly recommend creating any new indexers with the latest GA API version.

0 commit comments

Comments
 (0)