Forum Discussion
DAX Query Performance vs Nested Measures
Hi WishAskedSooner,
Glad to hear the suggestions were helpful.
When you get to the optimization phase, you might find these Microsoft resources handy for planning and prioritizing improvements:
Covers data model design best practices, column/cardinality tips, and storage mode considerations. Optimization guide for Power BI - Power BI | Microsoft Learn
Step-by-step guide on capturing and interpreting performance metrics. Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Microsoft Learn
This way, when you have the time to focus on optimization, you will have a solid starting point.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.
Hi WishAskedSooner ,
I am sorry to say that, yes, having nested measures CAN cause performance slowdown. As always, this is based on the types of functions in teh nesting and the volume of data. For example, if you are using "Sum" and "Sumx" in a lot of them you can end up costing memory / performance becuase of the way the Power BI engine works through the nesting.
If you use a lot of variables that might help out.
You couldn't use Performance Analyzer but before going through the pain of undoing everything, I would see if you can use DAX Studio and if it can help you find some issues.