Forum Discussion
Dax CPU Optimization for Capacity
- 2 years ago
ChrisCarrVictra This may give you better performance but it sounds like you need to optimize your Overall Points measure:
VAR Summary = SUMMARIZE ( CALCULATETABLE( 'Stores', 'Stores'[Area] IN { "East", "West" }, 'Stores'[StoreName] <> "VA-Bluefield" ), Stores[StoreName], "Overall Points", [Overall Points] ) RETURN RANKX ( Summary, [Overall Points],, DESC ) - Anonymous2 years ago
Your point of view is great Greg_Deckler . I have the following additions:
Hi, ChrisCarrVictra
If you need to optimize your complex DAX expressions, you can refer to the following article:
Optimizing DAX expressions involving multiple measures - SQLBI
In the following articles, there are tutorials for optimizing different DAX functions:
How to Get Your Question Answered Quickly
If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Greg_Deckler
😲 is this you who just suggested CALCULATETABLE or am I dreaming? 😅 Looks like you started to like the function 😂
tamerj1 Lol! I never had an issue with CALCULATETABLE. In fact, in my opinion, the No CALCULATE approach (VARs, Table VAR, Table Aggregator) without CALCULATE or CALCULATETABLE can solve probably 90% or more of all DAX problems. You add CALCULATETABLE and you are at 99.99% of all DAX problems solved. And, it's the exact same pattern it's just that you use CALCULATETABLE when creating your Table VAR. Still no CALCULATE though! 🙂