Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello,
I've been recently trying to improve the performance of my dashboard. As suggested in "Mastering DAX" course I changed one of the calculated columns into measure since it's a value that I'm not slicing on anywhere. It resulted in the size of the model reducing by 20MB (in DAX studio) and increase in loading time of main charts that use the measure by 200ms (Performance Analyzer).
Which one of the two should influence my decision on whether I should go with the measure or the calculated column?
Do I understand correctly that reduction in size of the model will reduce the refresh time but the loading time of the charts will still be longer (my main concern)?
Thanks
@PshemekFLK
As per your explanation, you should go with the measure solution as you want your users of the reports to have a better experience. Further, 20MB is subjective to the size of the total file size and the number of records, cardinality, and so on.
However, I hope you have set up your model in an optimum way and the measures have been written with performance in mind.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
Thank you for your reply. What do you mean by measure resulting in better experience? Should I ignore the fact the performance analyzer shows that the visuals will load slower?
@Fowmy wrote:
However, I hope you have set up your model in an optimum way and the measures have been written with performance in mind.
Yes, I tried to follow all the rules of star schema and optimize dax to the extent of my knowledge
.
Further, 20MB is subjective to the size of the total file size and the number of records, cardinality, and so on.
The total size of the model is 200MB, before it was 220 MB.
@PshemekFLK
As you mentioned "loading time of main charts that use the measure by 200ms", When you or your users use the dashboards/reports, it will have slowness in loading the visuals. I just noticed that you mentioned 200ms which is 1/5 of a second, if you feel the reports are performing without noticeable delay, I would suggest stick to the measure than the columns.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
61 | |
56 | |
55 | |
36 | |
34 |
User | Count |
---|---|
76 | |
73 | |
46 | |
45 | |
43 |