Power BI Embedded: Paginated reports extremely slow to export via REST APIs

[Meesha]

We are seeing extremely slow performance with this PowerBI Paginated REST API when calling it through Postman or a similar tool - GetExportToFileStatus API 

Exporting the same paginated report from Power BI service takes less than 10 seconds end to end. The MS Learn try it portal linked above also works much faster. But a simple BLANK report with no datasets/code/visuals requires about 30 seconds to render and export hitting the 3 available rest APIs listed below out of which 23 seconds are spend just on the second step (time between the creation of the export request and the "succeeded" status). Anything more complex will probably requires way more time (beyond several minutes). 

 Has anyone in the community encountered this issue? It seems very odd that there is so much difference in the performance between rendering a report on the service vs calling the REST APIs

 3 APIs 

Reports - Export Report In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn

Reports - Get Export To File Status In Group - REST API (Power BI Power BI REST APIs) | Microsoft Le...

Reports - Get File Of Export To File In Group - REST API (Power BI Power BI REST APIs) | Microsoft L...

Is there a way we can request more CPU/ressources for Power BI Embedded exports?

[v-yangliu-msft]

Hi  @Meesha ,

Suggest you use Power Automate's HTTP action to try placing the bearer token directly inside the request header, and then test whether the performance will be faster than a third-party API tool like postman? Because Power Automate is a tool provided by Microsoft to automate the running of a combination of Microsoft services and APIs, it can be realized that the return of the previous API is populated into the next API, see these links for details:

Using the HTTP action to make requests with Microsoft Flow - Microsoft Power Platform Blog

Overview of the cloud flows - Power Automate | Microsoft Learn

Best Regards,

Liu Yang

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

[llourens]

Liu Yang,

   Thanks kindly for the response, I work with Manisha on this project. 

   I would be surprised if that solution offered any improvement - the actual fields in the Export object returned by Get Export To File Status In Group indicate an average 23 second elapsed time between "CreatedDateTime" and "LastActionDateTime". I may be able to carve some time out today to implement this in Power Automate, but given that we have the response indicating that the processing time is so high on Power BI's side of things, I suspect we'll see the same behavior.

This is an unexpected performance hit that jeopardizes an entire project. We badly need to see that 23 seconds reduced to something more reasonable, such as the time that it takes to render the reports on Microsoft's own interface at powerbi.com, where it is a matter of seconds in the single digits.