Forum Discussion
Advocate IICapacity Query Memory Limit % not working
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!!
Super UserHi LeifB
What you have to remember is that due to having a 10% query memory limit, there are still some other lying factors that need to be considered when a query is running because it is not only memory that is being utilized but also CPU which would factor into it showing the 15% spark due to those other factors of the model running, getting the data, etc.
Advocate IIThanks, that makes sense. Do you know if there's a way to see the true % of memory being used? Or alternatively, approximately how much higher the percentage will go because of the "other factors"?
v-sathmakuriCommunity Support
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!!