Discussion:
[Bacula-users] Perfomance improvement moving from mysql 5.0 to 5.1 or 5.5?
Maria Arrea
2011-08-28 13:22:01 UTC
Permalink
Hello

We are using bacula 5.0.3 with mysql 5.0.77 on RHEL 5.7 x64. We are backing tens millons of file and we are staring to see performance problems with mysql. Our server has 6 GB of ram and 1 quad core Intel Xeon E5520 @2.27 Ghz.

We have converted from MyISAM to InnoDB in our mysql, and we have seen some performance improvements. Doe anybody know if migrating mysql 5.0 to 5.1 or 5.5 will improve performance with innodb? We have tried to migrate from mysql to postgresql with no luck (http://mtu.net/~jpschewe/blog/2010/06/migrating-bacula-from-mysql-to-postgresql/) though.

Maybe more ram would increase also performance? We are using my-innodb-heavy-4G.cnf as mysql config file.

Regards

Maria
Phil Stracchino
2011-08-28 17:15:31 UTC
Permalink
Post by Maria Arrea
Hello
We are using bacula 5.0.3 with mysql 5.0.77 on RHEL 5.7 x64. We are
backing tens millons of file and we are staring to see performance
problems with mysql. Our server has 6 GB of ram and 1 quad core Intel
We have converted from MyISAM to InnoDB in our mysql, and we have seen
some performance improvements. Doe anybody know if migrating mysql 5.0
to 5.1 or 5.5 will improve performance with innodb?
Oracle claims on the basis of their benchmarks that MySQL 5.5 is 150%
faster on Linux than MySQL 5.1, and 1500% faster on Windows.
Post by Maria Arrea
Maybe more ram would increase also performance? We are using
my-innodb-heavy-4G.cnf as mysql configfile.
How much RAM is in the machine? Most of the default config files are
next to worthless. Remember that MySQL started out as a SQL DB designed
for acceptable performance on machines with less than 32MB of RAM and a
single 32-bit CPU core of at most a couple of hundred MHz.

Is your MySQL running on a dedicated server, or does it share a box with
other applications? On a dedicated MySQL server, as a rule of thumb,
80%-90% of total system RAM should be allocated to MySQL, with 75% of
total system RAM in the InnoDB buffer pool.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
***@caerllewys.net ***@metrocast.net ***@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
Adrian Reyer
2011-08-28 19:44:33 UTC
Permalink
I went from
1. 4GB MySQL 5.1 MyISAM via
2. 16GB MySQL MyISAM via
3. 16GB MySQL InnoDB to
4. 8GB PostgreSQL 9.0

9M files in last full backup, 2TB data, 35 clients.
See Message-ID: <***@r2d2.s.lihas.de>
Subject: Re: [Bacula-users] Performance with many files
2011-08-11 and 2011-07-06 for the background.

Postgres works so far, but I am only at month 4 of 13 now. A noteable
difference is the time needed for spooling jobs to one of my 1GB-sized
File-volumes. At the beginning it had been >3*1GB/minute with MySQL, but
the performance constantly decreased and in the end it had been
1GB/3minutes with otherwise unchanged disk-parameters (iSCSI-volume).
With Postgres I run at 2-3*1GB/minute for 1 month now. The limit is the
iSCSI-part, which I will get rid of soon.

Regards,
Adrian
--
LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart
Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91
Mail: ***@lihas.de - Web: http://lihas.de
Linux, Netzwerke, Consulting & Support - USt-ID: DE 227 816 626 Stuttgart
Loading...