Sorry. It probably would of helped to include some of this information. It would be a large deployment in terms of what I have seen others using. There could be ~12 servers each with ~1,500 hosts and 300,000 service checks (almost all NSCA). We expect a lot of service checks per host so we want to keep the number of hosts homed to each server below 2,000. I hope this helps.
Thanks BTW if anyone has scalability documentation it would help us do some server sizing. -----Original Message----- From: Jason Gauthier [mailto:[email protected]] Sent: Thursday, July 08, 2010 9:11 AM To: Nagios Users List Subject: Re: [Nagios-users] Running Nagios on Vmware >Is anyone aware of documentation or test cases showing whether or not running Nagios on VMware is a good idea? I realize the common opinion is that it >is a bad idea due to I/O but I am looking for something a bit more in depth. >Thanks I think it depends on your environment. I'm running Nagios and Cacti on Hyper-V with 165 hosts and 487 services. It seems to be fine. Sometimes apache is slow to respond. ------------------------------------------------------------------------ ------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
