We run ours on a VM (ESX3.5sp2).  Running on SLES 10.2 32 bit on a IBM 346 with 
Dual Xeon 3Ghz and 10k disks in a internal RAID5.  As a reference point we 
currently have 563 devices and 27.46K data points on a single box.

Our biggest issue is getting a machine grunty enough to keep up.  It will take 
all the resources you give it.  Tried 64 bit but we didn't have enough RAM and 
CPU in the building to make it happy so we swapped back to 32 bit.  During the 
modeling process one of my CPU's maxes out and I regularly get localhost errors 
in the event console.  For some reason Zenoss only seems to use one of the 
CPU's even though I have given it 2.  One idles along at 9% and the other 
between 66% and 100%. When the CPU maxes out the graphs stop working. 
Particularly just after a reboot. I see gaps in the output and I have to 
disable notifications until it settles (which can be numerous hours).  On a 
slower or more stressed machine the zenoss daemons would stop running randomly 
as well because it couldn't keep up.  If I tell my SmokePinglike command to do 
more than 10 pings at a time (on 23 routers) this all happens at once and the 
CPU goes to 99.99% utilized and stays there.  Maybe this is your issu
 e.

I kept running out of RAM as well until I gave it 6Gb. Currently running at 
4.13Gb used at a relatively idle point. 

Give it a dedicated host machine unless you have a grunty beast with enough 
resources to dedicate to Zenoss.  I tried to share resources nicely with all 
the other nicely behaved guests. I ended up on my own dedicated host server as 
any other guests on the same machine would suffer badly because it stole all 
the CPU and disk access.  A higher spec server on a SAN may have fixed this.

I don't think our issues are VM related as it ran well for the short time I had 
it on a higher spec machine even with a couple of other idle VM's running 
along-side but the people that purchased it wanted it back. Dang!  Make sure 
your ESX is patched as when unpatched the disk access speed is terrible and 
Zenoss needs fast disks.  Ours is peaking at around 3MBps and is is regularly 
at 1.5MBps.  

Waiting for the budget to get a new higher spec one with faster disks.




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=31539#31539

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to