Forum Discussion

DouweMeer's avatar
DouweMeer
Impactful Individual
6 years ago
Solved

Optimize Service memory usage

So I have a report which has an incremental refresh on a Salesforce source. This Desktop report is published to Service which, fully loaded is approximaly 9GB on Service. This report is (currently) refreshed every 4 hours. I'm working on some other report to put on there as well in the excess of 7GB with a planned refresh of 4 hours and as the source an SQL database. 

 

Now the discussion I'm having with our Power BI Governance team is that we at corporate level are hitting the memory capacitiy of our node of 50 GB. We're having a discussion on slimming down reports but we struggle to define the memory usage in the first place. My argument is that when I would change my report from Import to Direct Query, it would in fact use much more memory as the table will be stored in Cache (Primary Storage aka Memory), while with Import it would be stored in storage (aka secondary storage). My argument would say that the current limitation is on the Memory and not the (secondary) Storage, thus having the report as Import is a better way to publish the report than using Direct Query. 

 

Everyone is making loads of assumptions, including myself on Memory usage and how storage would work on Service. Also the monitor dashboard created by Microsoft used by our Admins is limited in that the Memory usage can't be filtered to the report/ workspace.

 

One says Direct Query would be the Memory saver while the other (myself) says the import is the Memory saver. What is true?

  • JirkaZ's avatar
    JirkaZ
    6 years ago

    DouweMeer Exactly. And btw. the book "The definitive guide to DAX" explains the engine behind Power BI really well.

8 Replies