10 Replies Latest reply on Mar 13, 2013 2:39 PM by Leon Adato

    Polling Engine Capacity Planning?

    byrona

      I am trying to figure out how to do some capacity planning with my polling engines.  I have found several posts on how this may be done but I don't see any solid conclusions on a methodology.  Specifically, I need to know how this would be done when running multiple SolarWinds modules on these engines, not just NPM.  We are currently running NPM, SAM, IPAM and NCM and I need to know how to understand where my capacity limitations are and plan out when I will need to add an additional poller.

       

      Can somebody at SolarWinds please provide some insight on this, preferable a KB article or White Paper but just a response here would be a good start, thanks!

        • Re: Polling Engine Capacity Planning?
          byrona

          Somebody... anybody?

          • Re: Polling Engine Capacity Planning?
            Leon Adato

            My experience is that there are no hard and fast numbers to be able to pull to get the modeling you are talking about. I've got 8 pollers running NPM and SAM. On some of them they are spiked to 90% utilization (SolarWinds calculation of that) with 8000 elements. On another poller (same installation) I have 9000 elemnets but 70% utilization. Ditto for the SAM side of things.

             

            I know that can be a maddening answer, but some of it has to do with the complexity of the devices on the poller, the response time of the devices (an old 6509 will take much longer to report it's CPU than a new 2900); some has to do with the complexity of the data you are collecting (custom UnDP, SAM templates, etc); some has to do with teh polling frequency if you are adjusting it on a per-box basis; and some has to do with the module (NetFlow COULD hammer your system depending on how much data is being exported).

             

            ...and so on...

             

            My suggestion is to call your sales rep, get him to set up a conference with one of the engineers who is familiar with all the modules you have (or are considering) and they can give you a sense of what to expect.

             

            THEN as you are implementing, you need to keep a watchful eye on the stats. I have a custom report that pulls all the data into a single screen for all the pollers, so I can see at-a-glance how healthy my pollers are and when it's time to either move items around or load up a new one.

            1 of 1 people found this helpful