Forum Discussion
Power BI Premium: Split Processing vs Querying
In our current SSAS based architecture, we have 2 servers, one that loads data and processes the SSAS data models and then syncs it to a 2nd server. All dashboards point to the 2nd server so users are never impacted by all the processing work going on behind the scenes.
We had to do this because doing the processing and having the user queries hit the same server was causing significant performance issues for users when processing was taking place. This was mainly for a model that had about 50M rows and was taking about 20-30 mins to process.
While, things like incremental load and partition processing etc are ways to help reduce processing time, I was wondering if there was any provision in Power BI Premium to help avoid this problem when partitioning or incremental refresh is not an option.
1 Reply
Hi vickyd ,
When the refresh is in fact slow or crash, it can be due to several reasons:
- Insufficient CPU (refresh can be very CPU-intensive).
- Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are favorable to recommence).
- Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or gateway throughput. You may increase the capacity for workspaces to increase the model refresh parallelism frequency.
- Data volume - a good reason to configure incremental refresh, Incremental refresh can significantly reduce data refresh duration, especially for large model tables. See more: Incremental refresh in Power BI Premium .
See more details: https://docs.microsoft.com/en-us/power-bi/service-premium-capacity-optimize#why-are-refreshes-slow.
You may try to improve the performance for the data model, see:
Power BI performance best practices ,
Power BI Performance Tips and Techniques.
Best Regards,
Amy
Community Support Team _ Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
