I kind of figured MySQL might be part of it on the availability report. The tuning information would probably be good to put in the admin manual as there have been quite a few entries in the user's list of poor performance.
I'll give it a try and see what happens. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chet Luther Sent: Friday, May 09, 2008 4:23 PM To: General discussion of using zenoss system Subject: Re: [zenoss-users] RE: Replacing ZoDB On May 7, 2008, at 9:38 AM, Todd Davis wrote: > Has anyone ever made an attempt to replace the ZoDB backend in > Zenoss with > MySQL? > > With 158 devices, much of Zenoss is pretty much unusable. I might > as well > forget trying to run an availability report for the quarter as it > takes 15 > minutes to generate just the first screen (before I can change the > start > date). > > Sometimes, just pulling up a devices takes a good bit of time. As > much as I > like Zenoss and am REALLY wanting it to work, after a year I'm > seriously > considering dumping it as it's just not performing as it needs. > > What I'm wondering is if the choice to use ZoDB could be a large > part of the > performance problems. It definitely makes things difficult to deal > with > when upgrades fail. I have to say.. this question is very ironic. The availability report barely touches the ZODB at all. MySQL is doing all of the work to generate this report. If it runs slowly you need to tune your MySQL database as ZODB isn't the bottleneck. Check out this forum topic if you haven't already seen it: http://community.zenoss.com/forums/viewtopic.php?p=15266#15266 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
