> On 18/04/14 23:49, Lloyd Brown wrote:
>> At the moment, MyISAM.  I'd wondered if I could safely convert to
>> InnoDB, since that's generally going to have better locking
>> characteristics, etc.

As I've stated here before, it is my considered opinion that MyISAM
should no longer be in use in production databases.  Period.

You should have no problems whatsoever converting your Bacula DB to
InnoDB.  Just make sure that you have an adequate InnoDB buffer pool
before you start.  You should at this point be running nothing older
than MySQL 5.5, and in addition to setting innodb_buffer_pool_size as
large as you can, make sure innodb_buffer_pool_instances is set
appropriately (Oracle says the sweet spot is 3-4GB per buffer pool
partition), and also set these two variables:

innodb_flush_log_at_trx_commit = 2
innodb_autoinc_lock_mode = 2

These will significantly improve performance, especially under heavy
write traffic.


-- 
  Phil Stracchino
  Babylon Communications
  phils AT caerllewys DOT net
  phil AT co.ordinate DOT org
  Landline: 603.293.8485

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users