Version 2

    When monitoring the slowness site, Please watch your site for the next few days to figure out where to start:

    • The waits to load for 2 minutes, then loads; once loaded there is no performance issues. See Issue 1: machine.config
    • Site appears to be slow after about 20 minutes of not being used, but catches up after a few minutes. See Issue 2: IIS Timeout
    • Page loads, All charts take forever to load, then they simultaneously render at the same time. See Issue 3: All charts take forever to load.
    • 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.


    Issue 1: machine.config (Recommended 1st Step)

    Applies to Orion Core 2010 and higher.


    Symptom: Delay when calling Web Service from .Net Client.

    From your web browser, it may take a couple of seconds for the request to complete but when calling the same web method from a .net client it takes an extra 20 seconds.

    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.


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

    • Go into the following file location (location will always be the same):
      •   C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\Machine.config
    • Find this line, then insert the following below this line  --></system.serviceModel>



               <!-- Disable Autoproxy-->

                <proxy autoDetect="false"/>



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

    • Save the file. You may need to save to another directory, then move the file into the original location.
    • Reboot the Server for this change to take affect
    • Startup the Website and the loading should now no longer delay 120 seconds prior to loading.


    Issue 2: IIS Timeout


    Symptom: Browsing the Orion Web Console, you get Request Timed Out.


    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-2017

    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.



    Issue 3: All charts take forever to load.

    Symptom: The Disk configuration for the SQL Server, the Solarwinds Database or the TempDB is currently configured as a RAID 5 Array back-end or other similar disk array with write and read parity delays.


    Resolution: 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 geared towards performance like RAID 10 and not redundancy like RAID 5.



    Issue 4: SQL Requirements

    Symptom: 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.


    Resolution:  See Hardware Requirements