Skip to content

Commit d5cc5e0

Browse files
committed
new rsc size limit
1 parent 4c7408d commit d5cc5e0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/synapse-analytics/sql-data-warehouse/performance-tuning-result-set-caching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Once result set caching is turned ON for a database, results are cached for all
4141

4242
> [!IMPORTANT]
4343
> The operations to create result set cache and retrieve data from the cache happen on the control node of a Synapse SQL pool instance.
44-
> When result set caching is turned ON, running queries that return large result set (for example, >1 million rows) can cause high CPU usage on the control node and slow down the overall query response on the instance. Those queries are commonly used during data exploration or ETL operations. To avoid stressing the control node and cause performance issue, users should turn OFF result set caching on the database before running those types of queries.
44+
> When result set caching is turned ON, running queries that return large result set (for example, >1GB) can cause high throttling on the control node and slow down the overall query response on the instance. Those queries are commonly used during data exploration or ETL operations. To avoid stressing the control node and cause performance issue, users should turn OFF result set caching on the database before running those types of queries.
4545
4646
Run this query for the time taken by result set caching operations for a query:
4747

0 commit comments

Comments
 (0)