> > On Thu, Apr 25, 2013 at 11:41:37PM +0000, James Harper wrote: > > What could have gone wrong with my mysql to make this happen? I've > tried rebooting it. > > You very likely use MySQL with MyISAM tables. This is a very bad > combination for bacula. It will be better with InnoDB tables and > correctly tuned MySQL for these many inserts. However, postgres can be > tuned the same way and has the additional benefit of being able to use > parts of indices. As every insert has to update the tables and the > indices, you have way less writes with postgres. > I went the way MySQL 4GB MyISAM -> 12GB MYISAM -> 12GB InnoDB -> > Postgres 12GB myself.
I converted to innodb last time this happened. It didn't fix it but the problem went away by itself shortly after so I never got a chance to investigate further. James ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
