Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Power Bi Premium Gen2 : The evaluation reached the allowed cache entry size limit

Hello,   We are encountering an issue when we do a full refresh from the XMLA endpoint using a TMSL script.   We have a dataset size of 13Gb and we are in P2 capacity (50Go) so we shouldn't have ...
Need Help
v-yalanwu-msft's avatar
v-yalanwu-msft
Icon for Community Support rankCommunity Support
5 years ago

Hi, Anonymous ;

More details will help us understand your scenario better. Please let me know the information below.

1.What data source do you use and how do you connect it?

2.When do you get this error? Manually refresh or schedule refresh?

3.Do you have the refresh error for all datasets or the specific one?

4.Please check if your gateway is online.

 

In addition, You could try to increase the Maximum allowed (MB).

 

Cache Size for Power BI Desktop

It's good practice that before you schedule the report, you validate the complete dataset. One additional help for this, especially in the cases of larger datasets retrieved from the API, is to increase the cache limits. This increase can improve PowerBI's performance and stability. To configure this:

  1. Click Settings->Options->Global->Data Load to expose the "Data Cache Management Options".
  2. Try increasing the Maximum allowed (MB):to 16000 (or about double what the current setting is).
 

 

Reference: Known Issues and Limitations with Power BI.

Community Support Team_ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Hi v-yalanwu-msft, thanks for your reply. 

     

    I've already increase the Maximum allowed (MB) option in Data Cache Management.

     

    1.What data source do you use and how do you connect it?

    --> I'm getting the data from a datalake (Gen2), it's on the same region than the Power BI Capacity, I'm connected to it using the account key provided by the lake

     

    2.When do you get this error? Manually refresh or schedule refresh?

    --> This error happens only when I'm doing a full refresh (via TMSL script run via Runbook), when I'm doing an incremental refresh (less data) no problem

     

    3.Do you have the refresh error for all datasets or the specific one?

    --> Only on this specific one but it's the only large dataset I have (13Gb)

     

    4.Please check if your gateway is online.

    --> I don't have any gateway, everythins is on the cloud

     

    Thanks for your time