Web Interface Very Slow (9.1 SP5)

LTParis

I have had SolarWinds 9.1 (now at 9.1 SP5) installed on a virtual server (Citrix XenServer 5, 1 Processor, 1.5GB RAM) for about 7 months now, and the web performance has been degrading pretty rapidly over that time. Other aspects of the software, such as the stand alone applications, are all quite responsive so this seems to be a web UI only issue.

Are other users seeing a performance hit? For giggles here are some of the response times for simple web calls:

Landing Page - 18-30+ sec
Device Page - 45-70+ sec

Yann

Hi,

From Caroline:

Slow Web Console Performance

The Web console can be affected by the performance of IIS and the performance of the database.

The simplest method to determine where the issue might be is to load up to Login page. The login page itself doesn't query the database until the user has entered the credentials and attempted to log in.

 

Database

Timeout errors on the website occur because the SQL queries being run in the background might not have completed in the required time. If your database is quite large, or you are monitoring a large number of elements, the SQL server can become quite busy, which can slow down performance.

Each resource in the view on your pages requires a SQL query to run against the database - If you are experiencing trouble, sometimes the simplest way to solve it is to examine your website, and see if there are any resources on there that are rarely checked or required - if so, try creating a new view for those rarely-used resources, and use a Custom HTML resource to create a link to that view.

You can also change the timeout properties for the website. Open \inetpub\solarwinds\SWNetPerfMon.DB with Notepad, and scroll to the bottom. Here, you will see the timeout properties for the Connection, and for Database Commands. If you plan to edit these, please keep a backup copy of this file elsewhere. Next open IIS, expand Web Sites, Right-click on Solarwinds NetPerfMon, and go to Properties. Under the Web Site tab, you will see the IIS settings for Connection Timeout. This is 2 minutes by default, but can be increased if required.

You can also look into the performance of the database itself - on your SQL server, use the Performance Logs (perfmon.exe) to monitor the Disk Queue Length, to see if SQL is having trouble reading/writing to the disks fast enough. For more granularity, you can add counters to monitor the Disk queue length of each LogicalVolume on th server. Also check the size of your Transaction log file (.ldf) and the database itself. If you are running your SQL server on the same server as Orion, you might find that moving the database to another server alleviates the performance issues.

 

IIS

Check the Application logs for the following error:

Crypt32 Failed auto update retrieval of third-party root list sequence number from: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt> with error: 407 (HTTP Response Status)

This is a Warning message from a Microsoft component used in the Website, and if it does not have the ability to auto-update itself, it can cause a slowdown on the web console. The following Microsoft KB article can help: http://support.microsoft.com/default.aspx?scid=kb;[LN];317541

If you notice that the login page of the website is slow to appear the first time (for example, the first time each morning). This can be reproduced if IIS is restarted or if the Orion Website is not used for a few hours. It occurs because .net compiles the site at runtime - when IIS is restarted, or roughly 5 hours passes, the processes are recycled and the website will need to be compiled again. The website can be precompiled to resolve this, however, pre-compiling the website means you will need to pre-compile it with every change made - anytime the Configuration Wizard is run, upgrades etc.

Also, check the performance of the server that Orion is running on - the web console performance can be affected if IIS does not have enough resources. Use Task manager and perfmon to ensure that IIS is not limited by CPU and Memory while the web console is loading up.