nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Speeding up the web interface

ACDII

Is there a way to speed it up? I cant believe how slow it is to bring up the pages, considering the server is a dual CPU Dual core platform running 3.0Ghz.

Find more posts tagged with

Accepted answers

All comments

BryanBecker

You u need to describe your environment. For instance....what is the make up of your SQL server? # of elements? Anything else to describe ur set up.

BB

ACDII

I have about 2000 nodes, the SQL server is by itself on a 2000 platform, but I go over a T1 to get to it until I complete the installation, then they will be on the same network. Is the fact the SQL server is remote the problem?

vhcato

Response time between the NPM and SQL servers plays a huge role. While there are those who have had varying degrees of success with a distributed architecture over higher speed links with ~30ms response times (T3, OC3, OC12, etc.), it's generally not reccommended.

savell

The other thing you can do is purchase the additional web server, and install it on your database server.

Even with our database server and primary poller on the same local network, we found this helped our web response times greatly (4000+ nodes).

Sav.

BryanBecker

The recommendations would be put your web server as close to the DB server as possible. Like it's been said any latency between the 2 can give you the slowness you may be seeing. We have distributed polling where some pollers are over a WAN but the main NPM server and DB server are on the same network.

BB

njoylif

you also have to consider how many objects are on your maps and submaps. I was told that the more objects on the map and also submaps from that top page will affect how long it takes to load the page, as it has to do the appropriate queries. I am planning on breaking out my one TOP map into six different maps to increase web speed.

Network_Guru

I also suggest not having an "All Nodes" view on your home page.
My home page displays only node "exceptions" such as down, latency, packet loss, events and nodes above %80 CPU, Memory and Bandwidth utilization.

By Including the search for Nodes and search for Interfaces on the home page, you can find any node/interface or group of nodes/interfaces quite easily. I really don't see the need to view all nodes in a tree view on the home page.