Power BI Exchange

Please login or click SIGN UP FOR FREE to create your PowerBIUG account to join this user group.
Expand all | Collapse all

Report Issue with Performance

  • 1.  Report Issue with Performance

    Bronze Contributor
    Posted Nov 17, 2019 11:32 AM
    Hi All power bi Gurus,

    I have an issue with report having hierarchical slicer but when I open the report ,its taking long time to open the slicers and page ,is there any solutions to over come the performance.
    report connect with data lake files in azure.Please let me know if any suggestions to over come this issue.


    Academy - Online Interactive Learning from Experts

  • 2.  RE: Report Issue with Performance

    Posted Nov 18, 2019 07:44 AM

    You've given a very broad question, so I can only give you some VERY broad answers.  You need to do them in the following order:

    1. If you're doing any data shaping, do it as close to the data source as possible.  Great as Power BI is, it's always better to do in SQL server/Oracle/whatever
    2. Keep any tables in Power BI long and thin.  The wider (i.e. the greater the number of columns) a table is, the slower it will be.  Don't bring over any columns you don't need and delete columns as early as possible in your PowerQuery if you're going to do so
    3. If you create any columns, and there's a choice of doing it in either PowerQuery or DAX, do it in PowerQuery.  It will ALWAYS be more efficient.
    4. If it's possible to use Measures rather than Columns, use Measures.  They're more efficient
    5. If you have slicers that use Dates, use a Date Table.  These have an internal format that is optimised for slicing dates
    6. If a date doesn't need bringing back to a dashboard then don't bring it back

    Paul Jennett

    Academy - Online Interactive Learning from Experts

  • 3.  RE: Report Issue with Performance

    Silver Contributor
    Posted Nov 19, 2019 04:20 AM
    I think @Paul Jennett has given you really sound advice to work through.
    In an ideal world your data model in Power BI should be a star schema and containing only data you are using. This can often mean refactoring your data model as you start to build your report as you go along (and didn't have an exact plan to start with).

    The guys over at SQLbi.com have some really good training courses, 2 of which are  free for intro to PowerBI and Data Modelling. (https://www.sqlbi.com/training/).
    The Guy in the Cube have also released a video with Marco from SQLbi covering how to use VertiPaq ( https://www.youtube.com/watch?v=m34IOHcNPPo ​)
    VertiPaq is a bit of a numbers game, but it might help you understand what a good performant PBIX file might look like.

    (I have no affiliate with these guys, just both sets of people are really good learning materials)

    Robert Williams
    BI Developer
    Hemel Hempstead

    Academy - Online Interactive Learning from Experts

  • 4.  RE: Report Issue with Performance

    Posted Nov 19, 2019 12:52 PM
    Hi There,

    One thing about slicers that I learned is if you use the drop-down version is better for the performance, as it will just load the data when you click on on the slicer, therefore last time to refresh the page.

    About the refreshing in general, if you are using the same queries ( duplicated list or table from the same query for example) is much, much better if you "buffer" this source.

    Try to research about table.buffer and list.buffer, I would recommend the videos I have seen, but they are in Portuguese, I am sure you can find something in English on youtube.


    Fernando Camargo
    RG4 8BS

    Academy - Online Interactive Learning from Experts