Forum Discussion
Is this function written poorly?
- 9 years ago
Hi Jkaelin,
What is your actually problem with above DAX formula? What did you mean "looks poorly written (poor performance)"?
For its format, it looks tidy and clear. For its performance, it looks like not a complex logic. Acording to current information, this function look fine. Whether it is the best appropriate method, it depends on your detailed data in actual environment.
Here are some articles written about optimizing DAX performance:
Tune your PowerPivot DAX query, don’t use the entire table in a FILTER and replace SUMX if possible
Optimize DAX expressions involving multiple measures
Best regards,
Yuliana Gu
Hi Jkaelin,
What is your actually problem with above DAX formula? What did you mean "looks poorly written (poor performance)"?
For its format, it looks tidy and clear. For its performance, it looks like not a complex logic. Acording to current information, this function look fine. Whether it is the best appropriate method, it depends on your detailed data in actual environment.
Here are some articles written about optimizing DAX performance:
Tune your PowerPivot DAX query, don’t use the entire table in a FILTER and replace SUMX if possible
Optimize DAX expressions involving multiple measures
Best regards,
Yuliana Gu
- Jkaelin9 years agoResolver I
Thank you very much for the response. I will read those articles. I appreciate the feedback.
What did you mean "poor performance"?
I use this measure in a Power Pivot table for quarterly periods from 2000-2017 (about 60 periods) and the time it takes to calculate is about 20 seconds. If I use a derivative of that function to generate Stdev & Counts. It takes a little bit longer.
Thank you,
James k
- v-yulgu-msft9 years agoMicrosoft Employee
Hi Jkaelin,
Sometimes the long response time might also be related to the large amount of data.
Regards,
Yuliana Gu