Hello Team,
As outlined in the documentation link here. https://experienceleague.adobe.com/en/docs/experience-platform/query/guardrails
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. |
Batch Queries
| Query concurrency | Supported | N/A | Scheduled batch queries are asynchronous jobs, therefore concurrent queries are supported. |
Can somebody provide more insights on query performance behavior stats? What are the threshold defined by Adobe?. Here is the context and would like to know about it.
Let's say, business wants journey step events data inserted into the existing derived datasets (Max of 10-15 attributes in each record) for further engagements in future. Adobe's recommended way is to write data distiller queries and schedule the query if you need the data regularly.
1. 'N' number of concurrent batch queries are supported as mentioned in the document above. Lets assume each record has 10-15 attributes and this is the only custom batch query running in the platform, If query has to handle 4 million records each day, what's the execution time normally taken by query? Does adobe has a documentation to understand the natively built query service performance?
2. As mentioned in the document Maximum execution time is 24 hours? Also Does query service have restrictions on the number of records/size of data query can deal with? If yes, documentation link pls? If not, is there a adobe's recommendation on the data size?
3. Performance guardrail (Soft limit) - When exceeding performance guardrails, you may experience performance degradation and latency. Can adobe define the standard limits for concurrent batch queries, when one can expect performance degradation and latency for 'n' number of concurrent batch queries?
We understand its a cloud tool and depends on the query resources utilization, however looking for documentation where for given standard 'resources' allocation, what is the query service performance behavior?
