This issue can be caused by:
See the SolarWinds Technical Reference article entitled Best practices for managing your Orion database for troubleshooting information.
If the server hosting your SQL database is shared with multiple instances and used by several different applications, you will experience performance issues. SolarWinds recommends dedicating the server hosting your SQL database to the Orion application.
Ensure that all possible causes listed above are not contributing to the slow response time in the Orion Web Console. If these possible causes are not the problem, two possible causes are:
Grant the servername, <authenticated users>, and <network service> groups full rights to the following directories and all subdirectories:
Many applications (including Microsoft Access databases such as MIBs.cfg) may be configured to temporarily store files in the Windows temp directory. If these temporary files are not deleted and the Windows Temp directory grows to 64K, the SolarWinds Network Performance Monitor Service can no longer write the temp files it requires. When this issue occurs, the SolarWinds Network Performance Monitor Service will enter a loop where it tries to create a file that it cannot store anywhere. As a result, the service generates a CPU load up to 100%.
See Web Console is down due to high CPU utilization on the NPM Server for troubleshooting procedures.