Author: Heitor Faria <heitor AT bacula.com DOT br>
Date: Sun, 21 Dec 2014 12:24:00 -0300 (BRT)
Mr. Bacula Users, What do you think of those MySQL tuning hints for Bacula, specifically about this innodb_flush_log_at_trx_commit option? => http://www.innovation-brigade.com/index.php?module=Conten
Hello, just to add one more related question/problem to this thread: - using MySQL/MyISAM - about 15M files from several clients - 2.5-3M files per client - the problem: the Dir inserting Attributes
Author: Phil Stracchino <phils AT caerllewys DOT net>
Date: Sun, 21 Dec 2014 13:59:23 -0500
Truth is, innodb_flush_log_at_trx_commit = 2 should be the default option. innodb_flush_log_at_trx_commit = 1 is going to be slow whenever there is a very high rate of small commits, because every co
Author: Heitor Faria <heitor AT bacula.com DOT br>
Date: Sun, 21 Dec 2014 21:20:31 -0300 (BRT)
Thanks Phil! That was very enlightening. I think for Bacula type of workload is a very important MySQL setting to change. Do you have any information if for Postgresql using the synchronous_commit =
On 12/21/2014 11:17 AM, D S wrote: Hello, just to add one more related question/problem to this thread: - using MySQL/MyISAM - about 15M files from several clients - 2.5-3M files per client - the pro
Author: Phil Stracchino <phils AT caerllewys DOT net>
Date: Mon, 22 Dec 2014 11:20:31 -0500
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
Author: Oschwald Robert <robertoschwald AT gmail DOT com>
Date: Mon, 22 Dec 2014 18:08:54 +0100
For us, even InnoDB was way to slow. It took hours to insert attributes. We switched to PostgreSQL three years ago. Since then, no more performance problems. Also, creating the tree for restores was