Analyze memory usage in Power BI to improve performance

Last Updated on

Views: 5302 , Video Rating: 5.00 , View Time: 17:27 Minutes, # of Likes: 67, # of Disslikes: 0

In today’s video I will show you how to measure memory usage in Power bI.
We will go through a specific case where I improved the performance of a Google Analytics report created using Power BI.
We measured the size of the columns by using DMV queries in power bi and identified which columns where using up most of the memory.
This report was loading page speed data for more than 3 years and as those columns can not be compressed effectively by the power bi engine, they were making the power bi model very slow.
By loading less data and/or reduce cardinality of those columns, better performance can be achieved.

Link to DMV site:

Looking for a download file? Go to our Download Center:

SUBSCRIBE to learn more about Power and Excel BI!

– Join our DAX Fridays! Series:
– Power BI dashboards for beginners:
– Power BI Tips & Tricks:
– Power Bi and Google Analytics:

Contact us:


If you feel that any of the videos, downloads, blog posts that I have created have been useful to you and you want to help me keep on going, here you can do a small donation to support my work and keep the channel running:

Many thanks in advance!


► Linkedin:
► Twitter: @curbalen, @ruthpozuelo
► Google +:
► Facebook:



Analyze memory usage in Power BI to improve performance

7 thoughts on “Analyze memory usage in Power BI to improve performance”

  1. Hi Ruth – another excellent video, thanks ! This is great, I didn’t know you could do this. Unfortunately this does not work for me as either the database does not exists (which it does) or my user account does not have permission to access this. Any tips to get around this issue? Thanks Andrew.

  2. You just saved my life Ruth – I followed your video and found 2 columns causing so much memory usage due to their high cardinality. So way back in the SQL I changed columns like this "SUM(ISNULL(AmountColumn,0.0))" to this "SUM(CAST(ROUND(ISNULL(AmountColumn,0.0),2) AS NUMERIC(36,2)))" …… a small amount of accuracy is lost but the pbix file size shrinked from 137MB to 65MB !!!!!


Leave a Comment