Skip to content

Latest commit

 

History

History
89 lines (67 loc) · 5.71 KB

search-limits-quotas-capacity.md

File metadata and controls

89 lines (67 loc) · 5.71 KB
title description services documentationcenter author manager editor tags ms.assetid ms.service ms.devlang ms.workload ms.topic ms.tgt_pltfrm ms.date ms.author
Service limits in Azure Search | Microsoft Docs
Service limits used for capacity planning and maximum limits on requests and responses for Azure Search.
search
HeidiSteen
jhubbard
azure-portal
857a8606-c1bf-48f1-8758-8032bbe220ad
search
NA
search
article
na
11/09/2017
heidist

Service limits in Azure Search

Maximum limits on storage, workloads, and quantities of indexes, documents, and other objects depend on whether you provision Azure Search at a Free, Basic, or Standard pricing tier.

  • Free is a multi-tenant shared service that comes with your Azure subscription.
  • Basic provides dedicated computing resources for production workloads at a smaller scale.
  • Standard runs on dedicated machines with more storage and processing capacity at every level. Standard comes in four levels: S1, S2, S3, and S3 High Density (S3 HD).

Note

A service is provisioned at a specific tier. Jumping tiers to gain capacity involves provisioning a new service (there is no in-place upgrade). For more information, see Choose a SKU or tier. To learn more about adjusting capacity within a service you've already provisioned, see Scale resource levels for query and indexing workloads.

Per subscription limits

[!INCLUDE azure-search-limits-per-subscription]

Per service limits

[!INCLUDE azure-search-limits-per-service]

Per index limits

There is a one-to-one correspondence between limits on indexes and limits on indexers. Given a limit of 200 indexes, the maximum limit for indexers is also 200 for the same service.

Resource Free Basic S1 S2 S3 S3 HD
Index: maximum fields per index 1000 100 1 1000 1000 1000 1000
Index: maximum scoring profiles per index 100 100 100 100 100 100
Index: maximum functions per profile 8 8 8 8 8 8
Indexers: 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 2
Indexers: maximum running time 1-3 minutes 3 24 hours 24 hours 24 hours 24 hours N/A 2
Blob indexer: maximum blob size, MB 16 16 128 256 256 N/A 2
Blob indexer: maximum characters of content extracted from a blob 32,000 64,000 4 million 4 million 4 million N/A 2

1 Basic tier is the only SKU with a lower limit of 100 fields per index.

2 S3 HD doesn't currently support indexers. Contact Azure Support if you have an urgent need for this capability.

3 Indexer maximum execution time for the Free tier is 3 minutes for blob sources and 1 minute for all other data sources.

Document size limits

Resource Free Basic S1 S2 S3 S3 HD
Individual document size per Index API <16 MB <16 MB <16 MB <16 MB <16 MB <16 MB

Refers to the maximum document size when calling an Index API. Document size is actually a limit on the size of the Index API request body. Since you can pass a batch of multiple documents to the Index API at once, the size limit actually depends on how many documents are in the batch. For a batch with a single document, the maximum document size is 16 MB of JSON.

To keep document size down, remember to exclude non-queryable data from the request. Images and other binary data are not directly queryable and shouldn't be stored in the index. To integrate non-queryable data into search results, define a non-searchable field that stores a URL reference to the resource.

Queries per second (QPS)

QPS estimates must be developed independently by every customer. Index size and complexity, query size and complexity, and the amount of traffic are primary determinants of QPS. There is no way to offer meaningful estimates when such factors are unknown.

Estimates are more predictable when calculated on services running on dedicated resources (Basic and Standard tiers). You can estimate QPS more closely because you have control over more of the parameters. For guidance on how to approach estimation, see Azure Search performance and optimization.

API Request limits

  • Maximum of 16 MB per request 1
  • Maximum 8 KB URL length
  • Maximum 1000 documents per batch of index uploads, merges, or deletes
  • Maximum 32 fields in $orderby clause
  • Maximum search term size is 32,766 bytes (32 KB minus 2 bytes) of UTF-8 encoded text

1 In Azure Search, the body of a request is subject to an upper limit of 16 MB, imposing a practical limit on the contents of individual fields or collections that are not otherwise constrained by theoretical limits (see Supported data types for more information about field composition and restrictions).

API Response limits

  • Maximum 1000 documents returned per page of search results
  • Maximum 100 suggestions returned per Suggest API request

API Key limits

Api-keys are used for service authentication. There are two types. Admin keys are specified in the request header and grant full read-write access to the service. Query keys are read-only, specified on the URL, and typically distributed to client applications.

  • Maximum of 2 admin keys per service
  • Maximum of 50 query keys per service