is there a maximum number of addtiional slx pollers? what do people have? i have 4
Curious on how many interfaces you have per poller and what your db server looks like.. ex number of procs, ram, drive configurations and what your statistics summarization is set to. In a few months i will be turing up 1 SLX with 6 pollers.
hi there,
i am building a centralsied Orion install, so at the moment putting the back bone together before i migrate stuff to it. i currently have around 6,000 interfacesm 3,000 volumes, lord knows how many custom pollers, and around 1000 applications...
I am about to add arounf 15k interfaces, over 2k nodes when i install the 2 final pollers (to make 4)
The database runs ona windows 2003, SQL server 2005 cluster, running on a SAN, with 12 disks in a mirror. not the best SAN int he workld, but currently it flies....
what about you? what is your DB and pollers hosted on? ALl of my pollers and additional webserver are Vmware ESX VMs
I personally am not sure of the max number of pollers but I do know that you can squeeze about 10,000 elements onto a poller assuming its beefy. But all my boxes and my 2 pollers are blade servers. Here is my layout
Poller 1- 4400 elements 2300 APM elements
Poller 2 - 7000 elements
SQL Box - dual quad core, 10gb mem, 8 drives in a RAID 10 on a high performance SAN
We havent installed yet but it will look something we hope like.
1 SLX 6 pollers with 10k interfaces per running Win2k3 in a ESX VM
1 sql 2005 std server 8 proc 32 gig ram having log file on raid 10 san and data file on raid 5 san. not sure of the number of spindles on both.
I would stay away from RAID5 ESPECIALLY on the DB files. RAID5 will hit your performance pretty hard.
If you are going to have 10k elements per poller they need to be something like dual quad cores and 6+ GB of RAM.
From what I understand 10k elements is the absolute max a poller can handle effciently. The offcial limit is 8k keep in mind.
Oh also, I am not sure why this is but the DB files get slammed while the log files sit idle in comparison.
Officially there is no limit to the pollers capacity it comes down to the frequency of the polling and stats collection and of course the hardware.
You could have 15k elements but only poll every 5 minutes and pull stats every hour and the poller would cope but if you had 8k elements polled every 1 minute and pulled stats every 1 minute then the box wouldn't cope.
We had 9.5k elements polling every 5 minutes with stats collection every 5 minutes and the box was slow as a dog but rather than new hardware we increased the stats collection to every 20 minutes and the box is now a lot quicker.
Going back to the original question, I don't think there is a maximum number of pollers, it would greatly depend on the SQL server spec and disk space.
Are all your pollers on a single site or spread out over a number of sites?
So when you upped the stats collection interval to every 20 minutes, does that mean that it only gets a snapshot of the stats at the exact time, every 20 minutes, or does it have some way of averaging the stats over that 20 minute time period?
The reason I ask is becuase I have my stats collection set to 2 minutes right now, but the box is dog slow and the cpu stays a 90%+. I would thinking of upping the stats collection, but management wants the stats to be as granular as possible.
