
At the time of calculating measures, you can sometimes notice it (if the calculation takes a long time) that the CPU usage suddenly goes up to 100%, and after finishing the calculation goes back down.

Measures Consume CPUīecause Measure calculation should happen immediately after the interaction through other visuals, this calculation happens using the processing unit of CPU.

Every interaction like those will trigger the evaluation of a measure to happen. Measure calculation will happen on the fly, right at the time when you change a value in the slicer, filter, or click on a visual to highlight something. The only type of calculation in Power BI, which is not pre-calculated is the Measure. Let’s have a look at how Measure is calculated I have written in details about differences between Measures and Calculated Columns in this article, And I recommend you to read that article to get the full picture of what is the best type of calculation for your scenario. The other two types of calculations are Calculated Table and Calculated Column.

Let’s talk about the scenario that 99% of the time happens When you have measures in your table and matrix visuals, and you feel that it is slow, and sometimes VERY slow.Ī Measure is one of the three types of calculations you can create in Power BI. Having a badly designed model always hurts. That being said, I have seen models that even showing a column in table or matrix visual is slow, and the reason for that most of the time is bad design and bi-directional relationship.

Most of the time, you get the performance problem when you use Measures in the matrix or table visual. In this article, I’m going to explain why the matrix and table in your Power BI report might be slow, and what you should do about it? To learn more about Power BI, read Power BI book from Rookie to Rock Star. You have created a Power BI report with many visualizations and calculations, however, it is slow! And the slowest part of that is the report page with a matrix or table visual in it! Why that visual is so slow? Is this the problem of Visual in Power BI? or Power BI problem at all? or something to do with the modeling and calculation? I get this question a lot from my clients at the beginning of consulting work or from my students at my courses.
