cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
mjoanna Frequent Visitor
Frequent Visitor

Loading time

Dear community, 

 

I would like to ask, how long a report page is loading in average. We have multiple reports implemented in a customer environment and some pages react directly, on others there is a latency of 3 to 9 seconds. We already have minimized the visuals and measures, but some are necessary. 

We mostly have to different kinds of report pages:

  • One chart with 3 to 4 filters and 1 to 4 measures,
  • A page full of Sliders (~ 16 to 36) to calculate a measure or filter a view. 

We made the experience, that these sliders load quite long, but then other visuals or even textboxes are loading, too. Even if all interactions are deleted. 

 

Maybe you have some tips and tricks or an expert can tell me, if there is a known latency in the service like "All sliders need at least 2 seconds for loading because of something in the background" or "We are working on the loading time for visuals and it will be better with the next release" or .. you know what I mean. 

 

Thank you in advance.

 

p.s.: We already use a Power BI Premium capacity but this was not helpful at all. 

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support Team
Community Support Team

Re: Loading time

Hi @mjoanna ,

 

If you use DirectQuery mode to connect data, your report performance depends largely on the performance of the underlying data source.

 

You can optimize your data model using following tips:

 

  • Remove unused tables or columns, where possible. 
  • Avoid distinct counts on fields with high cardinality – that is, millions of distinct values.  
  • Take steps to avoid fields with unnecessary precision and high cardinality. For example, you could split highly unique datetime values into separate columns – for example, month, year, date, and so on. Or, where possible, use rounding on high-precision fields to lower cardinality – (for example, 13.29889 -> 13.3).
  • Use integers instead of strings, where possible.
  • Be wary of DAX functions, which need to test every row in a table – for example, RANKX – in the worst case, these functions can exponentially increase run-time and memory requirements given linear increases in table size.
  • When connecting to data sources via DirectQuery, consider indexing columns that are commonly filtered or sliced again. Indexing greatly improves report responsiveness.  

For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.

 

 

To minimize the impact of network latency, strive to keep data sources, gateways, and your Power BI cluster as close as possible. If network latency is an issue, try locating gateways and data sources closer to your Power BI cluster by placing them on virtual machines.

To further improve network latency, consider using Azure ExpressRoute, which is able of creating faster, more reliable network connections between your clients and Azure datacenters.

 

You can learn more via the link: https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance#optimize-your-model.

 

Best Regards,

Amy

 

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

3 REPLIES 3
Community Support Team
Community Support Team

Re: Loading time

Hi @mjoanna ,

 

To improve the performance , there are some tips you can considerate:

 

   Enable Row-Level Security (RLS) where applicable

   Use Microsoft AppSource certified custom visuals where applicable

   do not use hierarchical filters

   Provide data categorization for Power BI reports (HBI, MBI, LBI)

   Use the On-premises data gateway instead of Personal Gateway

   Use slicers sparingly

 

you can refer to the links to see more performance tips:

https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance,

https://blog.pragmaticworks.com/power-bi-performance-tips-and-techniques,

https://maqsoftware.com/expertise/powerbi/power-bi-best-practices.

(Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.)

 

Best Regards,

Amy

 

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

mjoanna Frequent Visitor
Frequent Visitor

Re: Loading time

Dear Amy, 

 

checked all of your tips and rebuild pages of our report. Some things were helping (such as reducing visuals on a page again), other we already worked on (no custom visuals, no hierarchical filters, ..)

 

I checked all with the help of the Power BI integrated Performance Analyzer. May be you or anybody else can now tell me, how can I improve the field "Other"? DAX and direct query figures are fine, but I have to wait 2 to 4 seconds for "other" (sometime even up to 7 sec).

 

Thank you in advance and best regards 

Community Support Team
Community Support Team

Re: Loading time

Hi @mjoanna ,

 

If you use DirectQuery mode to connect data, your report performance depends largely on the performance of the underlying data source.

 

You can optimize your data model using following tips:

 

  • Remove unused tables or columns, where possible. 
  • Avoid distinct counts on fields with high cardinality – that is, millions of distinct values.  
  • Take steps to avoid fields with unnecessary precision and high cardinality. For example, you could split highly unique datetime values into separate columns – for example, month, year, date, and so on. Or, where possible, use rounding on high-precision fields to lower cardinality – (for example, 13.29889 -> 13.3).
  • Use integers instead of strings, where possible.
  • Be wary of DAX functions, which need to test every row in a table – for example, RANKX – in the worst case, these functions can exponentially increase run-time and memory requirements given linear increases in table size.
  • When connecting to data sources via DirectQuery, consider indexing columns that are commonly filtered or sliced again. Indexing greatly improves report responsiveness.  

For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.

 

 

To minimize the impact of network latency, strive to keep data sources, gateways, and your Power BI cluster as close as possible. If network latency is an issue, try locating gateways and data sources closer to your Power BI cluster by placing them on virtual machines.

To further improve network latency, consider using Azure ExpressRoute, which is able of creating faster, more reliable network connections between your clients and Azure datacenters.

 

You can learn more via the link: https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance#optimize-your-model.

 

Best Regards,

Amy

 

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

Helpful resources

Announcements
Virtual Launch Event

Microsoft Business Applications October Virtual Launch Event

Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.

Power BI Helps Homeless and Trouble Youth

Power BI Helps Homeless and Trouble Youth

We spoke with Power BI Super User, Greg Deckler, about his charity work

MBAS Gallery

Watch Sessions On Demand!

Continue your learning in our online communities.

Users Online
Currently online: 424 members 5,046 guests
Please welcome our newest community members: