Forum Discussion
creating measures take long time
Having large datasets (~1 GB), creating new measures take vary long time, sometimes up to some minutes. It takes long time just from pusing the Create New Measure button untill the editor window is available as well as when the Measure is saved. Anyone else having the same issues and that knows the reason behind
Yes, again!
Whenever you create a measure, PowerBI reviews its dataset to see what could inflict the new measure.
Having an imported dataset of +1gb is not fun to work with.Is working with DirectQuery a possibility? This wil only load the data you actually use.
9 Replies
The reason is your dataset is way too large.
If you are working with a database, write some smaller queries to aggregate your data.
Thanks RobbeVL , but please note that it's not the measure execution time that is long, it the creation of the measures that takes a very long time. The same thing whenever I change a measure.
Imaging creating a measuer like below:
foo = true()
Creating this very simple measure takes 3-4 minutes all together. Yes I know my dataset is large, but there are reasons for that and we are looking into both aggregations and other teqniques to decrease the size
Yes, again!
Whenever you create a measure, PowerBI reviews its dataset to see what could inflict the new measure.
Having an imported dataset of +1gb is not fun to work with.Is working with DirectQuery a possibility? This wil only load the data you actually use.
Dear All,
I still have the same problem over 2 years later. Is there a proper solution nowadays?
Thanks!Just replying with some lernings.
Building larger datasets, use tabular editor
Even for smaller datasets, this is a problem if you have many calculated tables and columns. In that case, could you instead have used PQ for creating these calculated columns and tables? Yes... replacing a calculated table (based on another table) with a PQ table will most probably generate a slower ETL since PQ has quite a small cach and therefore will draw the same information a second time from the data source. Using PBI dataflows can help here in that case.
But... Doing all this work in a wherehouse or datalake is most time the best choise and then only do measures in PBI
