Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
SpiroswayGR
Resolver III
Resolver III

Powerbi Service is SLOW Today

Dear all,

 

Is anything wrong today with Europe server cause almost all reports not working and are soooo slow ? 

 

It was working perfect yesterday but today for no reason , not working as needed.

 

Kind regards,

Spyros

1 ACCEPTED SOLUTION
SpiroswayGR
Resolver III
Resolver III

Close the case... The problem identified on Premium per user capacity.

View solution in original post

2 REPLIES 2
v-yangliu-msft
Community Support
Community Support

Hi  @SpiroswayGR ,

Premium per user capacity is a good way, to determine whether the report hosting capacity often exceeds the capacity resource or the Hourly Query Duration Distributions function to view the ratio changes between colors to identify slow reports , And through observation to determine the reason for the corresponding slowness, for example, long-term operation consumes CPU, causing new queries to wait or users with a large amount of concurrent capacity are using the same report or data set, etc.

 

There are also reasons for slow power bi services:

1. When the report is refreshed at the same time, the model used for refreshing will be loaded. Once there are a large number of models in the memory, the memory will be full, so the model generated by the subsequent refresh operation will not be loaded and enter the queued state. , So that the report will be slow to load or even fail.

You can check the refresh time by viewing the Refresh Summary and metric usage app, make a reasonable allocation, try to choose the free time to refresh, and divide the refresh time together with the refresh time to avoid the queues caused by too many people and occupying resources.

2. The location of the gateway installation can have a significant impact on your query performance. Try to make sure that your gateway, data source locations, and the Power BI tenant are as close as possible to each other to minimize network latency.

For information, you can refer to the following:

https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-deployment-guidance

3.This report uses a complex Dax function, consumes too much memory, or uses too much of this post, especially the use of RLS, it will increase the refresh time.
You can also use the power Bi performance analyzer to view the performance of each report element or DAX studio to track the measurements in the data model and find problems.

 

This is related content, hope you can get help:

https://docs.microsoft.com/en-us/power-bi/admin/service-premium-capacity-scenarios

https://docs.microsoft.com/en-us/power-bi/guidance/report-performance-troubleshoot

https://docs.microsoft.com/en-us/power-bi/admin/service-admin-premium-monitor-capacity

 

Best Regards,

Liu Yang

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

SpiroswayGR
Resolver III
Resolver III

Close the case... The problem identified on Premium per user capacity.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors