On 12/22/14 11:01, Josh Fisher wrote: > MyISAM "can" be quick at inserting records at the end of a table, but > has both table locking and a single key buffer lock causing contention, > so is much, much slower at inserts that are not at the end of a table. > MyISAM also does not have a change buffer. In short, MyISAM is a poor > choice for an INSERT heavy application like Bacula. Use should use > InnoDB instead.
It is probably more accurate to say that MyISAM is a poor choice, period. It is a legacy storage engine that, honestly, should no longer be used in production. Even in a 100% read scenario, the best possible use case for it, it still underperforms compared to InnoDB. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: 603.293.8485 ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
