Hi @Djpitte ,
Please refer to this post to improve performance:
Does it only happen the first time or everytime?
Report server performance is affected by a combination of factors that include hardware, number of concurrent users accessing reports, the amount of data in a report, and output format.
General principles to consider include the following:
Report processing and rendering are memory intensive operations. When possible, choose a computer that has a lot of memory.
-
Hosting the report server and the report server database on separate computers tends to provide better performance than hosting both on a single high-end computer.
-
If all reports are processing slowly, consider a scale-out deployment where multiple report server instances support a single report server database. For best results, use load balancing software to distribute requests evenly across the deployment.
-
If a single report is processing slowly, tune report dataset queries if the report must run on demand. You might also consider using shared datasets that you can cache, caching the report, or running the report as a snapshot.
-
If all reports process slowly in a specific format (for example, while rendering to PDF), consider file share delivery, adding more memory, or choosing a different format.
-
To find out how long it takes to process a report and other usage metrics, review the report server execution log. For more information, see Report Server ExecutionLog and the ExecutionLog3 View.
-
For more information about how to mitigate performance issues by tuning memory management configuration settings, see Configure Available Memory for Report Server Applications.
-
Check DNS resolution, make sure to flush the cache first
-
What is the configuration information of the report server?
Once you have successfully migrated your report server to a new instance, you might want to perform the following steps to remove programs and files that are no longer necessary.
Uninstall the previous version of Reporting Services if you no longer need it. This step does not delete the following items, but you can manually remove them if you no longer need them:
-
The old Report Server database
-
RsExec role
-
Report Server service accounts
-
Application pool for the Report Server Web service
-
Virtual directories for Report Manager and the report server
-
Report server log files
Reference: SQL Server Reporting services 2019 Slow on new server
And here is another method may work:
(possible solution)
Hi all,
We experienced similar performance problems as described here. Loading portal pages took more than 30-40 secs, there were no CPU or SQL issues. Our on-prem Power BI Report Server (v. Jan 2019) is used by our co-workers in various locations/offices and behind a Amazon Route 53 DNS using a specific hostname. Then I got pointed in the right direction by using developer tools in Chrome returning some 401 http errors in the network tab.
It turned out all I had to do is add the hostname we are using to the registry of the Power BI RS and reboot the server. Please check the following kb article, for us Method 1 solved our problems.
https://support.microsoft.com/nl-nl/help/926642/error-message-when-you-try-to-access-a-server-locall...
Reference: power bi report server very slow
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
