Orion Core: Resolve Common Slow Website Issues

When monitoring the slowness site, Please watch the site for the next few days and let me know what you see more often:

• The waits to load for 2 minutes, then loads; once loaded there is no performance issues. See Resolution machine.config
• Site appears to be slow after about 20 minutes of not being used, but catches up after a few minutes. See Resolution IIS Timeout
• Page loads, but resources are missing data for a minute, then all suddenly load at the same time. See Resolution SQL Disk Performance
• Page with a lot of resources takes over a minute or returns Request Timed out. Pages with few resources load fine, and the settings page loads. See Resolution SQL Requirements

Note: If you have available resources and you are trying to figure out what to upgrade for better performance, upgrade the SQL Server first. I recommend to increase Disk Performance via array configuration or database drive sparation, then RAM, then CPU Last.

Resolution machine.config

Reason for the Cause. Microsoft .Net is required to go out to MS's website on the internet and check the .Net certificate. If the server does not have Internet Access or limited site browsing, this will cause this delay to happen quite often.

To Resolve: Modify machine.config to disable .Net framework from using the autoproxy feature.

1. Go into the following file location:
   •   C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\Machine.config
2. Find this line, then insert the following below this line  --></system.serviceModel>
   • <system.net>
   •         <defaultProxy>
   •            <!-- Disable Autoproxy-->
   •             <proxy autoDetect="false"/>
   •         </defaultProxy>
   • </system.net>

3. This is the last line in the config, and should be just after the new code --> </configuration>

4. Save the file.
5. Reboot the Server for this change to take affect
6. Startup the Website and the loading should now no longer delay 120 seconds prior to loading.
   

Resolution IIS Timeout

Reason for the cause: If the Orion web console was not being used heavily, IIS shuts down the worker process that handles requests from Orion's website every 20 minutes (this is the default value in IIS).

To change the default Values from 20 minutes to 1 full day of 1440 minutes.

Server 2008 and 2012 R2

1. Control Panel> Administrative Tools> IIS Manager
2. Expand out Local Computer
3. Select Application Pools
4. Right Click on SolarWinds Orion Application Pool and select Properties (or Advanced Settings for Server 2008)
5. In the Idle Time-out (minutes) box, type a number of minutes (you can set to 1440 for 1 full day), and then click OK.

Server 2003

1. Control Panel> Administrative Tools> IIS Manager
2. In IIS Manager, expand the local computer, expand Application Pools, right-click the Solarwinds Orion application pool, and then click Properties.
3. On the Performance tab, under Idle timeout, select the Shutdown worker processes after being idle for check box.
4. In the minutes box, type the number of idle minutes (with no processing requests) that you want to elapse before shutting down the idle worker process. The default value is 20 minutes. (You can set to 1440 for 1 full day)
5. Click OK.

Resolution SQL Disk Performance

Reason for cause: The Disk configuration for the SQL Server, the Solarwinds Database or the TempDB is currently on a RAID 5 Array backend or other similar disk array with write and read parity delays. It is recommended to run the SQL Database on a the very least a single simple disk, RAID 10 Array (4 Drive Minimum), or SSD drive configuration. RAID 50/60 and other complex setups can be utilized, but if you are reading this resolution, the current configuration is not cutting it, and does need to be reconfigured for another disk type.

Resolution SQL Requirements

Reason for Cause: The SQL Server currently setup is no longer capable of handling the amount of data being inserted, and the ability to access it to display on the Web Console. As versions cover more features and more modules are added to installations, it is always a good idea to look at the SQL Server configuration when this issue comes up. First look at the SQL Server performance History to see if Adding 2 CPUs or 4GB of RAM is required.

For Customers with Small Installs of 3 or less modules on entry License Tiers, these are my suggested smallest installs you can have:

Solarwinds Server:

The Solarwinds Server can be Physical or Virtual.

Microsoft Server 2008r2, 2012, or 2012r2 Web, Standard, or Enterprise

SQL Server 2008, 2008r2, 2012, or 2012r2 Standard or Enterprise

CPU: 6 Cores

RAM: 8 GB

Hard Drive OS: 80GB

SQL Server:

SQL Server can be Virtual or Physical. For Virtual, please make sure that dedicated resources are configured to the SQL Server.

Microsoft Server 2008r2, 2012, or 2012r2 Web, Standard, or Enterprise

SQL Server 2008, 2008r2, 2012, or 2012r2 Standard or Enterprise

SQL Server

CPU: 4 Cores

RAM: 12GB RAM

Hard Drives:

Drive 1 OS: 80GB

Drive 2 SQL Database: 100GB

For Customers that have All Modules Installed All at high Licensing Tiers, This is my recommended Requirements for a fast and efficient system:

     Note: This covers a base install with base Polling Rates. This will cover the majority of customers, but some may need to increase RAM or CPU for larger confiugrations.

Solarwinds Server:

The Solarwinds Server can be Physical or Virtual.

Microsoft Server 2008r2, 2012, or 2012r2

CPU: 8 Cores

RAM: 18-24 GB

Hard Drive OS: 80GB

SQL Server:

SQL Server can be Virtual or Physical. For Virtual, please make sure that dedicated resources are configured to the SQL Server.

Microsoft Server 2008r2, 2012, or 2012r2 Web, Standard, or Enterprise

SQL Server 2008, 2008r2, 2012, or 2012r2 Standard or Enterprise

SQL Server

CPU: 4 Cores

RAM: 24GB RAM

Hard Drives:

Drive 1 OS: 100GB

Drive 2 SQL Database: 250GB