From: "Jason A. Kates" <ja...@kates.org> > The day to day Mysql performance for normal Bacula operation is not > palatable with the indexes setup on the tables. (IE mysql is so slow > it's not usable with bacula IMO).
Mysql was "fast enough" for us until we got to ~150 million entries, but you MUST tune it and provide enough ram to operate without swapping. The defaults are intended for a small database on a desktop, sub-64Mb machine. Even the "large ram" sample uses a tiny amount of memory by today's server standards. I switched to Postgres for a number of reasons, but they don't really become a major driver for changing until there are ~50-100 million entries in the database. Below that MySQL has an advantage. Locking has never been a problem for us. As Kern has explained, it's only used on batch inserts. Having the extra indexes caused no noticeable slowdown on MySQL inserts, but was a huge win for dbcheck. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel