I had to think about how much memory/resources zenoss was using for our deployment recently, this is very rough but may be of interest:
zenoss 2.1.3, solaris 10 total about 1G of memory disk (and cpu) usage increases by set size with devices and monitors added memory/cpu/disk requirements == memory == running zenoss consists of 15 python processes and a mysql5 service. One larger python sefvice runs up to about 400M to 500M. 14 python services around 40M to 70M. mysqld 50 to 70M It adds up! Total just about 1G of memory == cpu == Quite light on cpu. (we do not monitor huge networks - maybe 40 devices (but with custom data collection for these devices that is heavier than normal)). There will be constant low additional load on cpu and network for snmp and stat/command monitoring. I can see cpu load does climb when someone is using zenoss web interface. Especially pages with multiple graphs probably cause most of our zenoss cpu load. == disk space == There are a few dependancies which need to be installed, which exactly varies. mysql5, python, netsnmp, various libs and utils, allow 500M-1G zenoss built package is 70M, bare install about 200M, allow 700M-3G for config, data, logfiles and mysql also. This includes logfiles/config/internal database, rrd databases, ... zenoss is good in that it itself looks after rotating logfiles and it limits databases to a set size. Everything monitored adds some disk space requirement (but is is a constant size that doesn't increase after initial add). So there should be no nasty surprise in a few months or years of running. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22015#22015 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
