Has anyone else seen this? Is it "expected"? I see a combination of mysqld, runzope and java at the top of a top list ordered by CPU but mysqld has taken by far the most time. I see cpu wait between 80 and 98% for a LONG time after zenoss stop / start - 20 minutes often. This isn't going into swap - I've upped the VM appliance from the shipped 2GB RAM to 3.5GB and there doesn't appear to be significant swapping contributing to this CPU wait.
The initial population could take some time, especially virtualized. I don't care what others say, v4 runs like dookie with less than 4GB of RAM. Even test instances.
I have a slew of optimization info on v4 if you need help once it's finished its init.
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.