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. Any ideas? -- Todd Davis <[EMAIL PROTECTED]> Sr. Network Administrator Associated Network Partners, Inc. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
