Unable to load model due to reaching capacity limits

[Kumarun]

We've started to be severly affected by error messages in our capacity.
Every 2 hrs getting this error msg while opening the report. How to resolve this.
Note: I'm using primium capaciy workspace

[FarhanJeelani · Accepted solution]

Hi @Kumarun ,

Can you please share what sku's you are using?

Check your usage metrics on azure portal at what time your reports are getting used widely.

Pickup the time points on which it was more than 80 % and then go to Fabric capacity metrics report.

look at the high usage and pick up the time point details for this and check which is causing the high usage either its interactive or background operations.

Blue is backgroud (ex: schedule refresh of reports)

Red is interaction by users (when end user using the reports).

Drill through the Time Points details and check which is actually using your resources and causing high usage and backlogs.

You can also check the frequency of the reports refresh. If report refresh is so frequent then check the total time it takes to refresh it in Monitoring hub and try to optimize the query and reports.

Please mark this as solution if it helps you. Appreciate Kudos.

[Poojara_D12]

Hi @Kumarun 

Frequent errors in a Premium capacity workspace, especially every 2 hours, often indicate resource limitations or overload in your capacity. This could be caused by high memory usage, inefficient DAX queries, complex visuals, or too many concurrent users. To resolve this, monitor your Premium capacity using the Power BI Premium Metrics App to identify resource bottlenecks, such as CPU or memory spikes. Optimize reports by simplifying visuals, reducing data model size, and improving query performance. Consider distributing the workload by scaling the capacity (e.g., upgrading to a higher SKU) or offloading less critical workloads to shared workspaces. Also, schedule refreshes during off-peak hours to balance resource usage.

 

[Anonymous · Accepted solution]

Hi @Kumarun ,

Thanks for reaching out to the Microsoft fabric community forum.

Following @FarhanJeelani 's suggestions, performing some basic immediate diagnostic steps may help resolve the issue. Additionally, I would like to include some more troubleshooting steps that may also address the problem:

Utilize the Power BI Premium Capacity Metrics App to monitor CPU, memory, and query activity every 2 hours during the error intervals. Concentrate on identifying if specific reports, datasets, or users are causing resource spikes.

Please follow the following documentation for mor details:

https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app

• Verify if any scheduled dataset refreshes, AI operations, or other background tasks are occurring at the same time as the errors. Concurrent workloads might lead to temporary capacity overload.
• Use the Performance Analyzer in Power BI Desktop to identify and optimize slow queries or inefficient DAX expressions, thereby minimizing resource consumption.
• Optimize your data model by eliminating redundant columns, reducing cardinality, and using appropriate data types for better performance and smaller dataset size.

Please refer to the below link for more details:

https://learn.microsoft.com/en-us/power-bi/guidance/power-bi-optimization

• If your dataset is large, enable incremental refresh to load only new or changed data, rather than refreshing the entire dataset. Monitor the impact of incremental refresh on capacity usage.
• If these optimizations are insufficient, consider upgrading to a higher Premium SKU (e.g., P2 or P3) to allocate additional resources.

Refer the below link for more information regarding SKU:

https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-what-is#capacities-and-skus

If I misunderstand your needs or you still have problems on it, please feel free to let us know. 

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

[Anonymous]

Hi @Kumarun ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[FarhanJeelani · Accepted solution]

Hi @Kumarun ,

Can you please share what sku's you are using?

Check your usage metrics on azure portal at what time your reports are getting used widely.

Pickup the time points on which it was more than 80 % and then go to Fabric capacity metrics report.

look at the high usage and pick up the time point details for this and check which is causing the high usage either its interactive or background operations.

Blue is backgroud (ex: schedule refresh of reports)

Red is interaction by users (when end user using the reports).

Drill through the Time Points details and check which is actually using your resources and causing high usage and backlogs.

You can also check the frequency of the reports refresh. If report refresh is so frequent then check the total time it takes to refresh it in Monitoring hub and try to optimize the query and reports.

Please mark this as solution if it helps you. Appreciate Kudos.