Forum Discussion

power_user_123's avatar
power_user_123
Frequent Visitor
3 years ago

suggestion needed to optimize report size

Hello!

In our project, we have 20 different individual reports with nearly 50 tables to serve these reports all together to go in a single .pbix file. The file size is already nearly 2GB. We are doing in import mode(our priority). As the file size has become very big, we are unable to move ahead with the development of the report. The performance of the report is very horrible. If we want to switch to either  direct query or composite mode, what will be the disadvatages? Any suggestions which mode is appropriate:Import/direct/dual? 
FYI: Our reports are mostly table visuals.

Thanks

3 Replies

  • Hi,
    You can go with Power Bi Dataflows so import your all table in Dataflows then after that import that dataflow in your pbix file so you get best dataset compression with increase in performance also and your dataset size will be nearly 300mb. I have used in my project it will help me alot

    Hope its Helpful !!!

  • KNP's avatar
    KNP
    Icon for Super User rankSuper User

    Difficult to answer with the information provided. It is very much an, "it depends".

     

    That said, things to look at.

    1. Do you actually need all 50 tables?
    2. Is it correctly modelled as a star schema? (this is critical)
    3. Have you removed ALL unnecessary/unused columns?
    4. Have you enabled incremental refresh on the large fact tables? (this, combined with setting the RangeStart and RangeEnd parameters to a smaller period should allow you to continue development and ensure quick refresh times once deployed to the service)
    5. Import mode is always preferred unless data is extremely large.
    6. Have you considered using Dataflows for the initial ETL?
    7. Have you separated the data model from the report files? (I assumed it is based on your comments)
    8. Do you have premium licenses?

     

     

    Questions.

    1. What is the datasource(s)? Does it fold?
    2. How many rows in your largest fact tables?
    3. What about the performance is "horrible"?

     

    Hopefully this will give you a few things to look at.