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 magnitudes faster with PostgreSQL.
It heavily depends on the number of files and attributes in t
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 buffe
On 12/21/2014 11:17 AM, D S wrote:
Re: [Bacula-users] Bacula MySQL Agressive Tuning
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
> > 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=Content&type=user&func=display&tid=1&pid=2
> > it seems to improve MySQL attribut
On 12/21/14 10:24, Heitor Faria wrote:
> 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=Content&type=user&func=display&tid=1&pid=2
> it seems
Title: Re: [Bacula-users] Bacula MySQL Agressive Tuning
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 action takes hours (5-6) - even more
