Forum Discussion
Continued ContributorDAX 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.
Super UserLike the Italians say – "It depends."
Nesting measures 3 or 4 levels deep isn’t a problem by itself. What does matter is what those nested measures are doing. If they contain expensive logic – like virtual tables, complex FILTER conditions, or heavy iterators (e.g. SUMX over FILTER) – then yes, performance can suffer.
But if each measure is relatively light (simple CALCULATEs, basic aggregations, context-preserving logic), unnesting won’t gain you anything noticeable. In fact, it might make your model harder to maintain for no real benefit.
Before you start rewriting everything, test the actual cost. DAX Studio is more reliable than Performance Analyzer in Mixed Storage Mode.
Details:
https://www.sqlbi.com/articles/optimizing-dax-expressions-involving-multiple-measures
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly