Power BI memory error message with Paginated reports visual

[Anonymous]

We've developed a Paginated Report with a parameter that allows the end user to specify the number of rows for download, integrated within the TOPN clauses. This parameter functions correctly in local executions.

However, after embedding the report in Power BI and executing it in Power BI Service, we encountered a memory error message, even when using a relatively small number like 6000. Monitoring the Task Manager during report execution, we observed a significant increase in CPU and memory usage.

Interestingly, when we execute the paginated report directly in Power BI Service, it handles over 70,000 records (almost the entire dataset) without issues or excessive resource consumption

Our question is: why does the visual of the paginated report exhibit this problem in Power BI? Is there a specific configuration setting that might be missing in Power BI?

[GilbertQ]

Hi @Anonymous 

What I can understand is that how the report renders in the Power BI service is because it is using shared resources (CPU and memory), whilst on your desktop it is using what you have available on your desktop hardware. 

It could possibly be using the TOPN is causing it to use more memory because it has to filter your data which requires more memory to scan to find the TOPN rows. Whilst if there is no TOPN it does not have to apply the filter.

[Anonymous]

Hi @GilbertQ, but we did not execute the report in the desktop version. Both, the embedded version in Power BI and the resport itself were executed directly in Power BI Service. That is why we do not understad this result. From Power BI (in power bi service) the report is not capable to provide the result with 5000 as TOPN, but executing only the report we do not have any problem with 78000 registers