Forum Discussion
Slow switch measure
yes indead the problem the switch option here, and thats a pretty sumply dax and seems good, try maybe making agregation table for both sums function that can give you a little boost on the performance for that dax meanwhile.
Yes, I could consider that option. But we have many dimensions as well, so the aggregated tables will still be large, unless I minimize the dimensions to filter on, which would be a large setback...
Hi D0minique ,
Taking into account that you have a large dataset and depending on the calculations you want maybe is good in terms of performance to check the aggregations:
https://docs.microsoft.com/en-us/power-bi/transform-model/desktop-aggregations
This can reduce table sizes so you can focus on important data and improve query performance. Aggregations enable interactive analysis over big data in ways that aren't possible otherwise, and can dramatically reduce the cost of unlocking large datasets for decision making
Thank you, MFelix. A good option to consider. StefanoGrimaldi mentioned this as well. However, we do have many dimensions as well, so the aggregated tables will still be large, unless I minimize the dimensions to filter on, which would be a large setback...
Hi D0minique ,
There're 10 mehtods to speed up your report. I don't know if it can help you a bit.
1. Only keep necessary visuals
2. Use integers instead of text values whenever possible
3. Stick to Power BI’s default visuals
4. Avoid both-directional relationships in your data model
5. Understand the difference between duplicate and reference queries
6. Only load data which will be reported upon
7. Slicers can be real performance killers
8. Overthink your data modeling technique
9. Split granularity to lower cardinality
10. Measure performance: Get a clear view on how a report is currently performing so you can quantitively measure and compare the outcome of any of your taken actions. Power BI has a built-in feature, called the performance analyzer, enabling users to measure how much time is spent on rendering visuals and how much time is spent on executing DAX code. It even gives you the full extract of the DAX code, which you can further analyze in tools as DAX Studio.About performance analyzer, you can refer to Use Performance Analyzer to examine report element performance.
And there're other Top 5 Power BI Performance Analyzer tools.
Also there's an official document you can refer to
Optimization guide for Power BI
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
but the agregation table dont related to the dimensional , when you set a aggregation its only linked to the fact table it will be using, aggregation tables arent used to do actual reporteing they are a backend lets say solution that speed up the information requestedon the fact table by the reports. or related to the dimensions itself as part of the table all depends on the approach
the only cons of aggregation tables lets say its they will growth the model size depending on the amount of data on it.
Oh, I understand now. Thank you for this clarification!
