Forum Discussion
Power BI high memory consumption when creating measures
Hi ItAccounts,
As d_gosbell said, normally this should more related to your data amount and calculate formulas that you apply on your data tables.
You can refer the following link to trace the dax formula(e.g. nested measure formula with iterator functions, multiple looping on whole table records...) that spends a huge amount of system resources and try to do some optimization on them to reduce the resource spend:
Use Performance Analyzer to examine report element performance
Optimizing nested iterators in DAX
In addition, you can also take a look at below document about tricks to improve power bi performance:
Optimization guide for Power BI
Regards,
Xiaoxin Sheng
I split a large report into 6 smaller reports and this problem went away, because each smaller report has fewer measures in it. The performance of the built-in Power BI measure editor is very poor, especially when a report contains a large number of measures. The built in measure editor still is not very fast after splitting up the report, but at least it does not use up so much memory that it causes Power BI to lock up.
I have started using Tabular Editor https://www.sqlbi.com/tools/tabular-editor/ to edit measures outside of Power BI because the built in measure editor is poor when editing large numbers of measures. Microsoft needs to improve its built in measures editor (one of the highest voted ideas for Power BI) and the Tabular Editor can provide some ideas for Microsoft. It should not be slow to edit measures or cause high memory consumption; is Power BI recalculating every measure in the report every time I add or edit a measure? There should be no need to do this.
- d_gosbell
Super User
ItAccounts wrote:
is Power BI recalculating every measure in the report every time I add or edit a measure? There should be no need to do this.
No, it's not. Measures are only evaluated when they are referenced in a query (and each visual can send one or more queries). Which is why I asked if you see this memory issue when editting measures while you have a blank page open as the visuals on the current report page will refresh after you change a measure in your model.
The number of measures will have some impact on the editor when it has to do the code completion prompts, but that should not have any real impact on memory usage. So it's likely that what you are seeing is related to some other issue, not directly an issue with editting a measure.
