Forum Discussion
Helper IVSlow visuals update on web published report
Hi qmestu ,
About caching, YES; Browser cache is stored and hence after the first visual render, Power BI fetches results from Browser cache and hence it is faster than first load.
You will need to optimize the report more since you are publishing to web. In this, your report is stored in shared capacity and hence it will take more time as compared to desktop or even normal workspace or Premium workspace. 60 pages are a lot for Power BI to render in shared capacity.
You can optimize more by the below tips:
1. Remove unwanted tables2. Remove unwanted columns/fields
3. Optimize DAX as much as possible - Use performance analyze + DAX Studio to get most optimized DAX
4. Try to avoid using dark colors
5. Try to minimize use of objects such as buttons, shapes, images, etc
6. Try to reduce the no. of pages in your report
Apart from this, try to publish the dashboard in a normal workspace and share with users since Publish to web is not such a good option since it has a lot of limitations associated and also the fact that sensitive data can be seen by anyone who has the link.
Give a Thumbs Up if this post helped you in any way and Mark This Post as Solution if it solved your query !!!
Proud To Be a Super User !!!
LinkedIn
Super UserHi qmestu ,
About caching, YES; Browser cache is stored and hence after the first visual render, Power BI fetches results from Browser cache and hence it is faster than first load.
You will need to optimize the report more since you are publishing to web. In this, your report is stored in shared capacity and hence it will take more time as compared to desktop or even normal workspace or Premium workspace. 60 pages are a lot for Power BI to render in shared capacity.
You can optimize more by the below tips:
1. Remove unwanted tables
2. Remove unwanted columns/fields
3. Optimize DAX as much as possible - Use performance analyze + DAX Studio to get most optimized DAX
4. Try to avoid using dark colors
5. Try to minimize use of objects such as buttons, shapes, images, etc
6. Try to reduce the no. of pages in your report
Apart from this, try to publish the dashboard in a normal workspace and share with users since Publish to web is not such a good option since it has a lot of limitations associated and also the fact that sensitive data can be seen by anyone who has the link.
Give a Thumbs Up if this post helped you in any way and Mark This Post as Solution if it solved your query !!! Proud To Be a Super User !!! |
qmestuI have already done most of what you mentioned. Sharing to specific users is not an option as this report is to be used on a public website.