I noticed that the loading speed of the RS portal ( the initial loading after logged in) became extremely slow after upgraded the report server from 14.0.* to 126.96.36.1992 version, tested using Chrome, Firefox and Edge.
I found out using the browser dev tools that the <servername>/reports/api/v2.0/me/ api was the main cause for such lagging, it appeared to be the authentication api if I'm not wrong?
I wonder if anyone else had faced the same problem, and is it my server's hardware performance issue or the report server's software issue?
We are encountering the same problem. For information it's the first time we are testing RS portal (188.8.131.528) with separate MS SQL Server 2016. The context is quite complicated because we are using cross domain authentication but the latency also come from <servername>/reports/api/v2.0/me/. For us it take arround 16 sec ...
We though it come from NTLM auth, so we tried to set up Kerberos auth with proper SPN and Kerberos delegation between RS portal service account and SQL server service account but still the same latencies 😕
I'm interested too if someone have any explanation to provide arround this topic !
I've the same problem. Power BI Report Server + SQL Server 2016 on separate machine and two domains. One domain for Power BI infrastructure and a second one for the office employes (domains are linked with a trust relation).
...and every call to api/v2.0/me is extremally slow (it tooks about 16s).
Did you find a solution for this problem?
I have the same issue. The average time to render the portal and its one folder is 40 seconds - Same API as posted.
If I navigate to the Web Service URL, the page loads immediately, however our clients prefer the interface.
Some details: Using Kerberos for authentication. SQL 2017 Backend on a seperate server. Verified all SPNs are valid and working. PowerBI Jan2019 v15
I am hoping someone found a solution, but forgot to post it. 🙂
We experienced the same 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.
I have the same problem. Power BI Report Server + SQL Server the same machine... and every call to api/v2.0/me is extremally slow (about 14s).
Did you find a solution?
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Learn about the exciting things that happened in July.
All Data Stories Gallery contributions are reviewed for each month. We select a contribution and feature the community member the following month.
Learn how to develop custom web applications for Power BI using .NET Core 3.1 and .NET 5.
We have great updates this month! Click the link for the video with more info.