Forum Discussion
DAX Performance
- Anonymous6 months ago
Hi Mcalderon98 ,
Since your report is using DirectQuery with Databricks and has 6 measures with 26 calculation groups inside an Inforiver matrix, the main performance problem is happening because there are too many calculation combinations. Each measure gets recalculated for every row, column, total, and each calculation group item, which creates heavy query load and large SQL queries in Databricks. To improve performance, try to reduce dynamic calculations and replace some calculation groups with normal measures wherever possible. Avoid complex DAX patterns like iterators or nested SELECTEDMEASURE() inside calculation items, and do not use high-cardinality fields in the matrix. Reducing the matrix detail level will also reduce the number of combinations. Use Performance Analyzer and DAX Studio to check whether the issue is in DAX or SQL. If SQL is slow, then optimize Databricks with better partitioning, indexing, or pre-aggregated tables. You can also use aggregation tables or hybrid mode, where summary data runs in Import and detailed data remains in DirectQuery. Overall, keeping calculations simple and reducing dynamic logic will improve performance in this scenario.
Refer these Microsoft Docs -
https://learn.microsoft.com/en-us/power-bi/guidance/directquery-model-guidance
https://learn.microsoft.com/en-us/power-bi/guidance/power-bi-optimization
https://learn.microsoft.com/en-us/power-bi/transform-model/aggregations-advanced
https://learn.microsoft.com/en-us/power-bi/create-reports/performance-analyzer
Hi Mcalderon98 ,
Since your report is using DirectQuery with Databricks and has 6 measures with 26 calculation groups inside an Inforiver matrix, the main performance problem is happening because there are too many calculation combinations. Each measure gets recalculated for every row, column, total, and each calculation group item, which creates heavy query load and large SQL queries in Databricks. To improve performance, try to reduce dynamic calculations and replace some calculation groups with normal measures wherever possible. Avoid complex DAX patterns like iterators or nested SELECTEDMEASURE() inside calculation items, and do not use high-cardinality fields in the matrix. Reducing the matrix detail level will also reduce the number of combinations. Use Performance Analyzer and DAX Studio to check whether the issue is in DAX or SQL. If SQL is slow, then optimize Databricks with better partitioning, indexing, or pre-aggregated tables. You can also use aggregation tables or hybrid mode, where summary data runs in Import and detailed data remains in DirectQuery. Overall, keeping calculations simple and reducing dynamic logic will improve performance in this scenario.
Refer these Microsoft Docs -
https://learn.microsoft.com/en-us/power-bi/guidance/directquery-model-guidance
https://learn.microsoft.com/en-us/power-bi/guidance/power-bi-optimization
https://learn.microsoft.com/en-us/power-bi/transform-model/aggregations-advanced
https://learn.microsoft.com/en-us/power-bi/create-reports/performance-analyzer
- Anonymous6 months agoNot applicable
Hi Mcalderon98 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
- Anonymous6 months agoNot applicable
Hi Mcalderon98 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.