App Performance
Factors to consider when looking at application performance
The Reporting Hub Application is fully installed within the customer's Azure environment. As such, there are many factors that can impact the performance of the application. The majority of these factors are within the control and responsibility of the customer. Below we have identified the main sources of performance issues.
Azure App Service metrics
Take a look at average CPU, memory and response times. This will give you an indication if the App Service plan you're currently on is sufficient to manage the load. If you find that response times continue to be a challenge, the below list are a few things you can try on your own before engaging Microsoft Support.
For more information on Azure resource monitoring please visit:
1. Restart the App Service
If your Azure App Service performance is degrading slowly over time, we recommend restarting your App Service after hours. This will clear any server cache and inactive sessions that may be tying up resources.
2. Check ARR Affinity
The Reporting Hub application is not stateless. This means that a user's session is tied to an instance of the App Service. If you are only running one instance, ARR affinity can be disabled. As users leave their browsers open and don't sign into the Reporting Hub, they leave sessions open on the App Service. These sessions tie up resources. To ensure these sessions get cleaned up periodically, we recommend disabling ARR affinity. ARR affinity is required when you have horizontally scaled out your App Service instances. You'll need to clear your browser cache and cookies as well to remove the ARR cookie. If not, you may get a "Login Failed: Can't Find UserName Or Organization" error message. You can test that it works by signing onto an Incognito window.
For more info see:
3. Scale up your Azure App Service
We recommend vertically scaling your App Service to provide more CPU and memory to handle your user load. Horizontally scaling is possible but you will need to scale back down to one App Service instance to update the Reporting Hub application. After update, you can scale out again to any number of nodes. Our clients have found that going from S1 to S2 improved performance significantly.
For more info see:
4. Custom DNS vs. *.azurewebsites.net
Many of our clients use a custom DNS for their Reporting Hub application. What we've found is the custom DNS routing can add delays which impact performance. These are typically seen during the sign-in process. You can compare accessing the Reporting Hub via the custom DNS and the default DNS set for the Azure App Service. The information should be helpful to understand any network differences that contribute to the slowness of the application response time.
Last updated