mike wrote: > On Mon, Dec 22, 2008 at 10:34 AM, Jeremy Zawodny <[email protected]> wrote: >> I think this could be valuable information that'd help make decisions about >> Drizzle usage in the Real World. In fact, if it is aged properly, you'd get >> a nice window into how folks are deploying it as time marches on and >> hardware evolves. That'd give us a bit better idea about what matters and >> what doesn't. > > +1 > > would also help little guys like me determine working configurations > and variables in comparison to the hardware being used.
Now this is an interesting idea. If we could collect more data, we could potentially have something develop an organic set of best-practices based on success or failure of different combinations of stuff... > I would bug people on the mysql forums trying to get this kind of > information. I'd definately include their IO scheduler, kernel > version, drizzle version, and personally I would find it useful to see > their configuration options (just make sure the ones that may hold > private information like username/password hardcoding or something > aren't transmitted) and perhaps a few things from a "status" output - > queries per second, for instance > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
