Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
I have very long loading times in my Report. I think the reason for this are different Slicers i have in the Report to switch in between two Visuals. For example 1 Visual shows customers by age and the second one show avergae costumer age. Is it better to use bookmarks to switch between those to Visuals or Slicers?
Solved! Go to Solution.
Hi @PBIRENE ,
I’d like to acknowledge the valuable input provided by the @Ritaf1983 and @Anonymous . Their initial ideas were instrumental in guiding my approach. However, I noticed that further details were needed to fully understand the issue.
Slicers allow users to filter data by selecting specific values from a predefined list. They provide an interactive way to control the data displayed on visuals, such as charts and tables.
Bookmarks capture and save the current state of the report page, including visuals, slicer selections, and other interactions. They allow users to create custom views and navigate between them.
In Power BI Desktop, you can see how each report element, such as visuals and DAX formulas, performs. By using Performance Analyzer, you can view and record logs that measure the performance of each report element as a user interacts with the report element, and which aspects of its performance are the most (or least) resource intensive.
You can view the execution of slicer and bookmark separately in your report and choose a more suitable solution. For more details, please refer to the documentation: Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Microsoft Learn
Best Regards,
Clara Gong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @PBIRENE ,
I’d like to acknowledge the valuable input provided by the @Ritaf1983 and @Anonymous . Their initial ideas were instrumental in guiding my approach. However, I noticed that further details were needed to fully understand the issue.
Slicers allow users to filter data by selecting specific values from a predefined list. They provide an interactive way to control the data displayed on visuals, such as charts and tables.
Bookmarks capture and save the current state of the report page, including visuals, slicer selections, and other interactions. They allow users to create custom views and navigate between them.
In Power BI Desktop, you can see how each report element, such as visuals and DAX formulas, performs. By using Performance Analyzer, you can view and record logs that measure the performance of each report element as a user interacts with the report element, and which aspects of its performance are the most (or least) resource intensive.
You can view the execution of slicer and bookmark separately in your report and choose a more suitable solution. For more details, please refer to the documentation: Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Microsoft Learn
Best Regards,
Clara Gong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Try adding a Apply button for the slicers to refresh the visuals.
Create Apply all and Clear all slicers buttons in reports - Power BI | Microsoft Learn
Hi @PBIRENE
In general, slicers should not cause performance issues.
You can check the difference with a performance analyzer.
Please take a look at the linked video :
https://www.youtube.com/watch?v=VFcDCls0la4
In addition to the points mentioned earlier, there are a few other factors that can affect slicer performance:
Model complexity: A complex model with multiple tables and relationships can lead to slower slicer performance.
Bi-directional and many-to-many relationships: Bi-directional and many-to-many relationships can also impact slicer performance.
Unnecessary columns: Including unnecessary columns in the dataset can increase the processing time for slicers.
Resource-intensive visualizations: Resource-intensive visualizations like maps can also slow down slicer performance.
Please check the linked video guides about model troubleshooting :https://www.youtube.com/watch?v=D9dm0-cp1_s&t=2s
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.