author | description | ms.service | ms.topic | ms.date | ms.author |
---|---|---|---|---|---|
baanders |
include file for Azure Digital Twins limits |
azure-digital-twins |
include |
03/21/2023 |
baanders |
The following table lists the functional limits of Azure Digital Twins.
Area | Capability | Default limit | Adjustable? |
---|---|---|---|
Azure resource | Number of Azure Digital Twins instances in a region, per subscription | 10 | Yes |
Digital twins | Number of twins in an Azure Digital Twins instance | 2,000,000 | Yes |
Digital twins | Number of digital twins that can be imported in a single Import Jobs API job | 2,000,000 | No |
Digital twins | Number of incoming relationships to a single twin | 50,000 | No |
Digital twins | Number of outgoing relationships from a single twin | 50,000 | No |
Digital twins | Total number of relationships in an Azure Digital Twins instance | 20,000,000 | Yes |
Digital twins | Number of relationships that can be imported in a single Import Jobs API job | 10,000,000 | No |
Digital twins | Maximum size (of JSON body in a PUT or PATCH request) of a single twin | 32 KB | No |
Digital twins | Maximum request payload size | 32 KB | No |
Digital twins | Maximum size of a string property value (UTF-8) | 4 KB | No |
Digital twins | Maximum size of a property name | 1 KB | No |
Routing | Number of endpoints for a single Azure Digital Twins instance | 6 | No |
Routing | Number of routes for a single Azure Digital Twins instance | 6 | Yes |
Models | Number of models within a single Azure Digital Twins instance | 10,000 | Yes |
Models | Number of models that can be imported in a single API call (not using the Import Jobs API) | 250 | No |
Models | Number of models that can be imported in a single Import Jobs API job | 10,000 | No |
Models | Maximum size (of JSON body in a PUT or PATCH request) of a single model | 1 MB | No |
Models | Number of items returned in a single page | 100 | No |
Query | Number of items returned in a single page | 1000 | Yes |
Query | Number of AND / OR expressions in a query |
50 | Yes |
Query | Number of array items in an IN / NOT IN clause |
50 | Yes |
Query | Number of characters in a query | 8,000 | Yes |
Query | Number of JOINS in a query |
5 | Yes |
The following table reflects the rate limits of different APIs.
API | Capability | Default limit | Adjustable? |
---|---|---|---|
Jobs API | Number of requests per second | 1 | Yes |
Jobs API | Number of bulk jobs running concurrently (including import and delete) | 1 | Yes |
Models API | Number of requests per second | 100 | Yes |
Digital Twins API | Number of read requests per second | 1,000 | Yes |
Digital Twins API | Number of patch requests per second | 1,000 | Yes |
Digital Twins API | Number of create/delete operations per second across all twins and relationships | 500 | Yes |
Digital Twins API | Number of create/update/delete operations per second on a single twin or its incoming/outgoing relationships | 10 | No |
Digital Twins API | Number of outstanding operations on a single twin or its incoming/outgoing relationships | 500 | No |
Query API | Number of requests per second | 500 | Yes |
Query API | Query Units per second | 4,000 | Yes |
Event Routes API | Number of requests per second | 100 | Yes |
Limits on data types and fields within DTDL documents for Azure Digital Twins models can be found within its spec documentation in GitHub: Digital Twins Definition Language (DTDL) - version 2.
Query latency details are described in Query language. Limitations of particular query language features can be found in the query reference documentation.