Forum Discussion
Questions regarding Power BI report performance
I have some simple questions regarding power bi report performance.
- About how many report pages are acceptable before the power bi report starts having performance issues?
- For the report developer, about how many "book marks / buttons" are acceptable before performance issues could occur?
- Any differences perfomance wise in placing a drop-down slicer on a page vs. a Chiclet slicer button?
- Any differences performance wise in a slicer on a report page vs. using the same slicer from the filter panel?
I'm interested in if the number of report pages and number of slicers / bookmarks associated with a page are affecting performance.
Hi mike12345
Your questions cannot be answered as "black and white" , like most power bi masters speaking when it comes to performance issues "it depends...".
Regarding pages, it really depends on the types of graphs you have there. The more "interactive" the graph is, the more resources are required.
Maps and graphs with animations, for example, consume a lot of resources.As for bookmarks, there is a limit of up to 20 in any case; this depends on what is in them, so it may be worth considering a page navigator to move between pages.
Recent versions have developed this feature.A regular slicer or a Chiselet the same chislet is more interactive and has the ability to add images so it will need more resources.
The filter consumes fewer resources than the slicer.Since it's really required to check by your report, I'm attaching links to more information on these topics.
https://www.youtube.com/watch?v=kkIXtvU1AiM
https://www.youtube.com/watch?v=1lfeW9283vA
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
1 Reply
Hi mike12345
Your questions cannot be answered as "black and white" , like most power bi masters speaking when it comes to performance issues "it depends...".
Regarding pages, it really depends on the types of graphs you have there. The more "interactive" the graph is, the more resources are required.
Maps and graphs with animations, for example, consume a lot of resources.As for bookmarks, there is a limit of up to 20 in any case; this depends on what is in them, so it may be worth considering a page navigator to move between pages.
Recent versions have developed this feature.A regular slicer or a Chiselet the same chislet is more interactive and has the ability to add images so it will need more resources.
The filter consumes fewer resources than the slicer.Since it's really required to check by your report, I'm attaching links to more information on these topics.
https://www.youtube.com/watch?v=kkIXtvU1AiM
https://www.youtube.com/watch?v=1lfeW9283vA
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly