Below are the specs of our setup\configuration. Any throughts on it and how I have the pollers setup? Anything you would recemmend changing? Our home page is setup for only 10 users who have it displayed all day long to watch for problems (refresh every 2 minutes). We are also using CPU/application/and node e-mail alerting.
From the engines table in our database:
elements - 1078
nodes - 117
interfaces - 403
volumes - 558
pollers - 1581
maxpollspersecond - 25 (seconds)
maxstatpollspersecond - 35 (seconds)
nodepollinterval - 15 (seconds)
interfacepollinterval - 60 (seconds)
volumepollinterval - 120 (seconds)
nodestatpollinterval - 2 (minutes)
interfacestatpollinterval - 5 (minutes)
volumestatpollinterface - 5 (minutes)
pollingcompletion percentage - 92.88847%
Home Page Modules Setup:
All Nodes - Tree (AJAX)
Top 50 Nodes by Physical Memory Used
Down Nodes
Nodes with Problems
Down Applications
Top 25 Nodes by CPU Load
Active Alerts
Top 10 Nodes by Current Response Time
Now our seperate SQL server CPU is almost always pegged at or near 100%, it is a 2GHz Quad Core with 2GB memory. Everything is DOG slow, browsing web pages etc on our SolarWinds site. When I shutdown SolarWinds the SQL server CPU drops to 5% - 10%. We are running NPM version 9.1 and APM version 2 SP1. I plan on installed AMP 2 SP2 tonight.