Guardrail types
There are two types of default limits within this document:
Guardrail type | Description |
---|---|
Performance guardrail (Soft limit) | Performance guardrails are usage limits that relate to the scoping of your use cases. When exceeding performance guardrails, you may experience performance degradation and latency. Adobe is not responsible for such performance degradation. Customers who consistently exceed a performance guardrail may elect to license additional capacity to avoid performance degradation. |
System-enforced guardrails (Hard limit) | System-enforced guardrails are enforced by the Real-Time CDP UI or API. These are limits that you cannot exceed as the UI and API will block you from doing so or will return an error. |
The default limits outlined in this document are constantly being improved. Please check back regularly for updates.
Primary entity performance guardrails
The tables below provide the recommended guardrail limits and descriptions for query execution when using a particular query pattern.
Ad hoc queries
Guardrail | Limit | Limit type | Description |
---|---|---|---|
Maximum execution time | 10 minutes | System-enforced guardrail | This defines the maximum output time for an ad-hoc SQL query. Exceeding the time limit to return a result throws the error code 53400. |
Concurrent Query Service users |
| System-enforced guardrail | This defines how many users can create sessions concurrently for a particular organization. If the concurrency limit is exceeded, the user receives a Session Limit Reached error. |
Query concurrency |
| System-enforced guardrail | This defines how many queries can be executed concurrently for a particular organization. If the concurrency limit is exceeded, the queries are queued. |
Client connector and result output Limit |
Client Connector
| System-enforced guardrail |
The result of a query can be received through the following means:
Note: Adding a limitation to the output count may return results faster. For example, |
Results returned via | Client UI | N/A | This defines how the results are made available to the users. |
Batch queries
Guardrail | Limit | Limit type | Description |
---|---|---|---|
Maximum execution time | 24 hours | System-enforced guardrail | This defines the maximum execution time for a batch SQL query. The processing time of a query is dependent on the volume of data to be processed and query complexity. |
Concurrent Query Service Users for Unscheduled Batch |
| System-enforced guardrail | For unscheduled batch queries (for example CTAS/ITAS queries in interactive mode), this defines how many users can create sessions concurrently for a particular organization. If the concurrency limit is exceeded, the user receives a Session Limit Reached error. |
Concurrent Query Service Users for scheduled Batch | No user limitation | N/A | Scheduled batch queries are asynchronous jobs so there is no user limitation. |
Computational hours for batch data processing | As specified in the Customer’s Adobe Experience Platform Intelligence Query Custom SKU Sales order | Performance guardrail | This defines the scoped amount of computational time per year a customer is allowed for executing batch queries to scan, process, and write data back into the data lake. |
Query concurrency | Supported | N/A | Scheduled batch queries are asynchronous jobs, therefore concurrent queries are supported. |
Client connector and result output limit |
Client Connector
| System-enforced guardrail |
The result of a query can be made available using the following methods:
Note: There is no upper limit to the record count number from the query result. |
Results returned via | Dataset | N/A | This defines how the results are made available to the users. |