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

A good time to seperate the poller and database?

We are starting to see some sluggishness on the Orion server which also has the database on it. I'm not sure if it because the maps are detailed, or the number of elements we are monitoring, or something else for that matter. Here is where we are :

Network Elements 3986 Elements
Nodes 520 Nodes
Interfaces 2967 Interfaces
Volumes 499 Volumes

Server Info :

OS Name Microsoft(R) Windows(R) Server 2003, Standard Edition
Version 5.2.3790 Build 3790
System Model ProLiant DL380 G3
System Type X86-based PC
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~3057 Mhz
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~3057 Mhz
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~3057 Mhz
Processor x86 Family 15 Model 2 Stepping 9 GenuineIntel ~3057 Mhz
Total Physical Memory 3,072.00 MB
Available Physical Memory 627.73 MB
Total Virtual Memory 7.85 GB
Available Virtual Memory 3.37 GB
Page File Space 4.85 GB
Page File C:\pagefile.sys

We've got a pretty beefy box here. We are expecting to add another 1000 elements by end of year. Wondering if now would be a good time to split the DB off to a new server or keep it on this server and get a smaller box to just be the poller?

Thoughts?

BB

Find more posts tagged with

Accepted answers

All comments

Network_Guru

Hey Bryan,

Your Orion install is very similar to mine as far # of interfaces & nodes.
Same server hardware & RAM, but my CPU's are only 2 Ghz.
One improvement I made earlier this year, was to install 3 new drives in Raid 5 & move the DB onto it's own drive. I found there was a lot of contention for spindle time when we were using the same drive for the OS, Poller & DB.
Also I'm still running V7.6, and I've found compacting the DB tables indexes once in a while seems to improve the DB performance.
How big is your DB?
I've found it can grow quite large if you don't optimize it once in a while, and this will affect performance. Also if you have a lot of web users &/or reports being refreshed, this too can affect performance.
I'd say you should be borderline ~ OK adding another 1000 elements, depending on your polling intervals.

-=Cheers=-
NG

BryanBecker

Current DB size is 10.5GB.

I do have the jobs in to compact the DB.

I'm currently running 30/30 for max interface/node polls per sec and max stat collections per second.

Thanks.

BB