Forum Discussion
Upgrade of Service for Ressource Governing
- 2 years ago
Yes but "heaviest" is quite relative.
In Measure Killer we have the "What if Analysis" which shows you that. But you might want to also take a look at the query times of those measures via DAX Studio etc to see how long it actually takes to query. It would be a good idea to test one measure at a time like this.
I would do it in the browser in the Power BI Service because there you will see when you hit the memory limit. So try to reduce the filters/measures in the visual that is creating this error and see when it happens to pinpoint what the bottleneck is.
I think an A2 has a maximum of 2GB of memory available so that might be too much as well.
Do you know which query is causing this?
Try to reduce the number of visuals and pin point a DAX expression that might be heavy.
Also I would suggest you to run external tool Measure Killer to remove all unused columns and measures from your model to improve overall performance.
I have already ran measure killer and i have 100% of usage for all measure and fields in the query.
The only thing i can't seem to be able to find is what are the heaviest measure to try to optimize them. Is there a way to find the weight of each measure?
- Brunner_BI2 years agoImpactful Individual
Yes but "heaviest" is quite relative.
In Measure Killer we have the "What if Analysis" which shows you that. But you might want to also take a look at the query times of those measures via DAX Studio etc to see how long it actually takes to query. It would be a good idea to test one measure at a time like this.
I would do it in the browser in the Power BI Service because there you will see when you hit the memory limit. So try to reduce the filters/measures in the visual that is creating this error and see when it happens to pinpoint what the bottleneck is.