Report slowness with multiple users opening at same time

[Anonymous]

Hello all,

We have one Organizational Survey Power BI report which is being used by many users (almost 150 -200+) at a same time, after the 3-4  of result announcemnt. During this time report become to slow to response and even few users are not able to open it.

This report is going to publish in couple of weeks. Last year too many users reported the issue.

This report uses the data from various excel sheets, we are using import mode. There are few complex measures used to show the data result. We have tried few options to handle this situation like -

1.  Moving other reports from this premium capacity to other capacity 

2.  Set up Power BI Premium autoscale setting.

We have opened the report by 30-40 people and it started loading slowy but it was not enough to add additional capcity using autoscale.

Any suggestions, in order to avoid such situation, How can we improve the performance/slowness of report. Any ideas.

Thanks in advance.

[mahoneypat]

Please share more info about the measures and visuals used in the slow report.  You likely either need to reduce the # of visuals (and therefore the # of concurrent calculations to be performed), and/or optimize the DAX measures used to make them more performant.

Pat

[Anonymous]

Thank you @mahoneypat for the reply.

This report is developed by some third party and after analysis and running Performance analyzer found that Card visual is taking lot of time to load. there are around 20-30 card visuals used in 2-3 pages and Matrices.DAX seems to be ok. I tried to use Card visual by okviz, it loads faster but could not sort as we wanted.

This report is survey reports of different units in organization, so Senior people check this on the day/week of result. During this time it hangs up.

Yesterday we again performed the load testing and added 4 additional v-coure to hande the load. After 60-70 concurrent users load at a time it used all the 4 additional load and was performing ok, but again starts loading slowly. Management do not want to change the visuals, so we suggested to release the result unit wise in phases to mitigate the load and add more additionla v-core (this is adding cost though)

any other suggestions/comments, welcomed. Thank you.

[mahoneypat]

Moving to a multi-value visual like the OKViz one would be the right direction (so fewer queries are being sent with each slicer click/load).  How complex are the DAX measures in the cards?  If complex, is the performance fine with very simple measures?  If so, please share your DAX and optimizations can be suggested.

Pat