The Premium capacity settings allow to limit queries in terms of memory usage and execution time (timeout). However, there is no such setting to limit CPU footprint for individual queries.
Therefore, a single poorly designed query can eat up all available CPU and cause throttling for an entire capacity. A new “Query CPU limit in %” setting could help reducing noisy neighbor effects caused by overly expensive queries.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
email subscription screenshot size
would be great if we have a control to resize the screenshot of a report/dashboard for email subscription. the default size is too small and hard to read/understand unless you open the attachementRodgie_Robles2 hours agoNew MemberNeeds Votes186Views9likes2Comments
Portable Library of Queries (Functions)
Currently, a custom connector requires a Data Source and a Authentication record associated to a function in order to be Published or exposed in the 'Get Data' dialog/window. This is perfectly fine f...3 hours agoNot applicablePlanned1.7KViews147likes14CommentsPower BI: Subscriptions & bookmarks in org apps
The subscription is a valuable feature. Please make it available in the Org App. The Org App hase many advantages, but it misses the subscription and bookmark features as in the classic app or report...StefanGrossen5 hours agoNew MemberNew166Views4likes1CommentNotebook Activity must support Notebook name resolution within a dynamic workspace
## Requested behavior The Fabric Pipeline Notebook Activity should support selecting a notebook by a stable Notebook name while the Workspace ID is dynamic. Example: - Workspace ID: `@pipeline()....EXXAVRM7 hours agoNew MemberNew12Views0likes1Comment