-
- Enthusiast
- Posts: 42
- Liked: never
- Joined: May 23, 2011 8:38 pm
- Full Name: Keith Kleiman
- Contact:
Collector architecture
We currently are monitoring 1900 agents and are using 5 collectors to monitor them. I am in the process of building our new SCOM 2012 architecture and am rethinking about doing them same for my nworks architecture. I am considering rather than using collector servers with SCOM agents to act as a proxy, but instead to use two dedicated management servers to act as my collectors for the benefit of performance. My question is what kind of a performance benefit can I anticipate approximatly? Some benefit, substantial benefit? 10% 90% etc...? I would like to reduce the number of collector servers while maintaining the ability to adequatly monitor. Thanks!
-
- Expert
- Posts: 226
- Liked: 28 times
- Joined: Jan 27, 2012 11:31 am
- Full Name: Hani El-Qasem
- Contact:
Re: Collector architecture
Hi Keith,
Results can be variable, but a Management Server<->Collector can comfortably scale to between 1.5-to-2 times the capacity of an Agent<->Collector.
Hope this helps
Results can be variable, but a Management Server<->Collector can comfortably scale to between 1.5-to-2 times the capacity of an Agent<->Collector.
Hope this helps
-
- VP, Product Management
- Posts: 1497
- Liked: 384 times
- Joined: Jan 01, 2006 1:01 am
- Contact:
Re: Collector architecture
Hi Keith,
I would definitely recommend Management Servers, instead of agents. It is difficult to put a precise number on the performance increase; but because Management Servers write direct to the SCOM database, without having to use local queue cache as an agent does, then they will perform much better.
I would say that you can definitely monitor (with full functionality) using three MgtServer-Collectors, instead of the five you have now. And that will give you headroom for some future growth also.
BTW - Our next major MP update is almost ready for beta - and that will have some huge performance and scalability improvements. I'll be dropping you a line about our beta program very soon!
Regards
Alec
I would definitely recommend Management Servers, instead of agents. It is difficult to put a precise number on the performance increase; but because Management Servers write direct to the SCOM database, without having to use local queue cache as an agent does, then they will perform much better.
I would say that you can definitely monitor (with full functionality) using three MgtServer-Collectors, instead of the five you have now. And that will give you headroom for some future growth also.
BTW - Our next major MP update is almost ready for beta - and that will have some huge performance and scalability improvements. I'll be dropping you a line about our beta program very soon!
Regards
Alec
-
- Enthusiast
- Posts: 42
- Liked: never
- Joined: May 23, 2011 8:38 pm
- Full Name: Keith Kleiman
- Contact:
Re: Collector architecture
Thanks Hani and Alec
-
- Influencer
- Posts: 17
- Liked: 2 times
- Joined: Jul 02, 2012 8:30 am
- Full Name: Nico Weytens
- Location: Belgium
- Contact:
Re: Collector architecture
just a quick reply,
We also moved away from regular collectors/agents to Management Servers a while back, and have changed the amount of objects 1 collector can handle from 5000 to 12500.
The MSs HW spec is 2 vCPUs and 8GB of RAM.
We're still on 2007 R2 though, but hope it helps.
We also moved away from regular collectors/agents to Management Servers a while back, and have changed the amount of objects 1 collector can handle from 5000 to 12500.
The MSs HW spec is 2 vCPUs and 8GB of RAM.
We're still on 2007 R2 though, but hope it helps.
-
- Enthusiast
- Posts: 42
- Liked: never
- Joined: May 23, 2011 8:38 pm
- Full Name: Keith Kleiman
- Contact:
Re: Collector architecture
Nico, Appreciate you sharing your experience. Thanks again! Keith
Who is online
Users browsing this forum: No registered users and 2 guests