Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
We're looking to deploy some PBI reports to our field managers that are connected to a live SSAS tabular instance. However slicing and filtering data in reports on either the IPad and through the browser is very slow – around 7 seconds per interaction
In attempting to improve performance, we
Can anyone help?
Is the SSAS tabular instance on the same network as the Desktop? If so, it would be an interesting test to put Desktop on a virtual machine in Azure (IaaS) and then see if it suffers from similar performance lag and if so, then reduce the visualizations and see if you get the same performance improvement. Basically what this will tell you is whether it is something about the Desktop that is just faster than the apps/web or if it is network connectivity between Azure and SSAS tabular instance.
It is either that or just the layers of abstraction involved when going from a desktop application to an app/web app. At that point, those things are interacting with web services and the like that the Desktop probably does a lot more efficiently. In an app and web, there is likely a lot of javascript involved, so there's a scripting engine involved versus compiled code. It's going to be slower.
I have helped some customers that have had performance issues with many visualizations on a report, in particular, interconnected slicers, where changing one slicer affects all of the other slicers, or a good portion of them. However, the ability to improve this is often directly tied to how things are being done in the model, the relationships behind the scenes, etc. Before delving into that, it would be interesting to rule out network latency.
thanks for your replies - apologies for the delay in responding.
i took some additional actions, such as :
The conclusion appears to be that PBI (IPad and browser) do not handle single values in cards very well, graphs with nothing on the axis, or treemaps with single values and no groups.
In one report with many cards and single valued treemaps or graphs with no members on the axis (i.e. just 2 measures), changing
• all cards to graphs with multiple members on the axis,
• all graphs to graphs with multiple members on the axis ,
• all treemaps to have multiple members in the groups,
reduced response times from 7 seconds to 2.
I'll raise it to the PBI team and see if they can optimise this
cheers
If you've got snappy responses on desktop and fast execution in profiler traces, then the bottleneck is the round-trip latency and throughput between your datacenter and the Azure datacenter your reports live on.
Since minimizing the number of visualizations brought the response time down the most, my guess is that it would be throughput rather than latency as your bottleneck. Hopefully someone will see this who can speak better to how you might go about narrowing down the issue from here.
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.