Forum Discussion
Capacity Query Memory Limit % not working
- 27 days ago
Hi LeifB ,
Sorry for the delay in response.
At present, there’s no way to view the exact governed-memory percentage for an individual query. The Capacity Metrics app doesn’t provide a per-query memory-limit metric. On an F256, the configured 10% Query Memory Limit is approximately 10 GB, however, the percentage displayed for an operation in the Metrics app should not be interpreted as the exact amount of memory used against that limit. Microsoft also hasn’t documented a fixed overhead or percentage that explains how far the displayed value may exceed the configured limit. so, we shouldn’t assume that a reading of 15% means the query used 15 GB of governed memory. The clearest indication that the query-memory limit has actually been exceeded is a resource-governance / query-memory-limit error.
How to configure workloads in Power BI Premium - Microsoft Fabric | Microsoft Learn
Thanks!!
Hi LeifB,
The key point here to understand that
The 10% Query Memory Limit does not mean the entire F256 capacity can never show more than 10% memory utilization.
The setting controls the maximum memory available to an individual DAX/MDX query for temporary/intermediate results, not a hard cap on the total memory that the semantic-model workload can consume.
Microsoft describes Query Memory Limit as the maximum percentage of available memory that can be used for executing an MDX/DAX query.
So if you see 15%+ capacity memory usage does not, by itself, demonstrate that the 10% limit was bypassed.
In your F256 example
An F256 has 100 GB maximum memory for semantic-model workloads, and the documented SKU maximum memory per query is 10 GB.
If you configure:
Query Memory Limit = 10%
you should think of that as a query-level resource-governance limit, rather than:
"This semantic model/report is allowed to consume only 10% of the F256's memory."
If this helps, ✓ Mark as Kudos | Help Other
- LeifB1 month ago
Advocate II
I am not referring to the overall usage when I say "spikes of over 15%", in my second screenshot there are six individual queries that are showing as over the 10% limit. I'm wondering why those individual queries are allowed to exceed the threshold.