Agrégateur de flux

FromDual has the pleasure to announce the release of the new version 1.1.1 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.1.0 to 1.1.1 # cd ${HOME}/product # tar xf /download/myenv-1.1.1.tar.gz # rm -f myenv # ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/
Upgrade from 1.0.5 to 1.1.1 # cd ${HOME}/product # tar xf /download/myenv-1.1.1.tar.gz # rm -f myenv # ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.1 MyEnv

• Function to check upgrade requirements to v1.1 implemented.

MyEnv Installer

• none

MyEnv Utilities

• none

MySQL Backup Manager

• End tag added to mysql_bman code in certain places where it was missing.
• innodbackup bug fixed, pigz bug fixed.
• Warning message more verbose explaining solution in case of missing xtrabackup binaries.
• pigz as alternative compression mechanism implemented.
• Log mysqldump error to stderr.
• my_exec replaces exec/system calls.
• Return code exits fixed.
• Cleanup date is formated nicer and cleanup bug is fixed.
• copy_preserve introduced to preserve timestamp and archive code cleaned up.
• Retention time can be 0 or any value out of h, d, w, m.
• Binary log begin and end ts is written to log file.

MySQL Backup Manager Catalog

• Catalog DB handle was sometimes called without a catalog (ugly bug introduced in v1.1.0!).

Taxonomy upgrade extras: myenvoperationMySQL Operationsmulti instanceconsolidationBackupcatalogrelease

Taxonomy upgrade extras: myenvoperationMySQL Operationsmulti instanceconsolidationBackupcatalog

FromDual has the pleasure to announce the release of the new version 1.1.1 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.1.0 to 1.1.1 # cd ${HOME}/product # tar xf /download/myenv-1.1.1.tar.gz # rm -f myenv # ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/
Upgrade from 1.0.5 to 1.1.1 # cd ${HOME}/product # tar xf /download/myenv-1.1.1.tar.gz # rm -f myenv # ln -s myenv-1.1.1 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.1 MyEnv

• Function to check upgrade requirements to v1.1 implemented.

MyEnv Installer

• none

MyEnv Utilities

• none

MySQL Backup Manager

• End tag added to mysql_bman code in certain places where it was missing.
• innodbackup bug fixed, pigz bug fixed.
• Warning message more verbose explaining solution in case of missing xtrabackup binaries.
• pigz as alternative compression mechanism implemented.
• Log mysqldump error to stderr.
• my_exec replaces exec/system calls.
• Return code exits fixed.
• Cleanup date is formated nicer and cleanup bug is fixed.
• copy_preserve introduced to preserve timestamp and archive code cleaned up.
• Retention time can be 0 or any value out of h, d, w, m.
• Binary log begin and end ts is written to log file.

MySQL Backup Manager Catalog

• Catalog DB handle was sometimes called without a catalog (ugly bug introduced in v1.1.0!).

FromDual has the pleasure to announce the release of the new version 1.1.0 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.0.5 to 1.1.0 # cd ${HOME}/product # tar xf /download/myenv-1.1.0.tar.gz # rm -f myenv # ln -s myenv-1.1.0 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.0 MyEnv

• Error with !includedir fixed (Bug #143).
• tput is hidden in interactive mode now. No more nasty warning messages.
• Start/stop script did not pass error code correctly.
• Timezone complain on myenv_start_stop.php fixed with temporary fix.
• Init script should not through errors on SuSE any more.
• Init script is improved. Myenv should only start if network is available (runlevel).
• mysqladmin complains now if my.cnf has wrong parameters and does not show the schema down any more.
• MYSQL_HOME was changed from basedir to datadir, consider this for upgrade, this is a significant change, impact is not clear!
• Under some circumstances up did not show all schemata, fixed.

MyEnv Installer

• No changes.

MyEnv Utilities

• NUMA maps script from Jeremy Cole added.
• block_galera_node.sh fixed for more than 1 back-end.

MySQL Backup Manager

• For many backup types cleanup, archive and compress functionality added.
• Schema backup per-schema writes log pos now to log file and catalog.
• Binlog policy added.
• Backup structure is not created any more for cleanup and catalog operations.
• Binlog backup should work now with and without default location.
• Passing strange characters in password is handled more robust now.
• Schema names more robust with back-ticks.
• memory-table-check bug fixed.
• Command line is displayed in output (without exposing password).
• Cleanup of archivedir is possible now.
• Backup for configuration file implemented.
• Physical backup based on xtrabackup/mysqlbackup implemented.
• All exit's replaced by returns. Proper error handling should be possible.
• Backup logging implemented.
• Password from command line is not exposed any more to log file. Back-port from v1.0.5.
• Per schema privilege backup implemented.

MySQL Backup Manager Catalog

• Catalog creation and catalog upgrade integrated.

Taxonomy upgrade extras: myenvoperationMySQL Operationsmulti instanceconsolidationBackupcatalogrelease

FromDual has the pleasure to announce the release of the new version 1.1.0 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.0.5 to 1.1.0 # cd ${HOME}/product # tar xf /download/myenv-1.1.0.tar.gz # rm -f myenv # ln -s myenv-1.1.0 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.0 MyEnv

• Error with !includedir fixed (Bug #143).
• tput is hidden in interactive mode now. No more nasty warning messages.
• Start/stop script did not pass error code correctly.
• Timezone complain on myenv_start_stop.php fixed with temporary fix.
• Init script should not through errors on SuSE any more.
• Init script is improved. Myenv should only start if network is available (runlevel).
• mysqladmin complains now if my.cnf has wrong parameters and does not show the schema down any more.
• MYSQL_HOME was changed from basedir to datadir, consider this for upgrade, this is a significant change, impact is not clear!
• Under some circumstances up did not show all schemata, fixed.

MyEnv Installer

• No changes.

MyEnv Utilities

• NUMA maps script from Jeremy Cole added.
• block_galera_node.sh fixed for more than 1 back-end.

MySQL Backup Manager

• For many backup types cleanup, archive and compress functionality added.
• Schema backup per-schema writes log pos now to log file and catalog.
• Binlog policy added.
• Backup structure is not created any more for cleanup and catalog operations.
• Binlog backup should work now with and without default location.
• Passing strange characters in password is handled more robust now.
• Schema names more robust with back-ticks.
• memory-table-check bug fixed.
• Command line is displayed in output (without exposing password).
• Cleanup of archivedir is possible now.
• Backup for configuration file implemented.
• Physical backup based on xtrabackup/mysqlbackup implemented.
• All exit's replaced by returns. Proper error handling should be possible.
• Backup logging implemented.
• Password from command line is not exposed any more to log file. Back-port from v1.0.5.
• Per schema privilege backup implemented.

MySQL Backup Manager Catalog

• Catalog creation and catalog upgrade integrated.

Taxonomy upgrade extras: myenvoperationMySQL Operationsmulti instanceconsolidationBackupcatalogrelease

Taxonomy upgrade extras: myenvoperationMySQL Operationsmulti instanceconsolidationBackupcatalog

FromDual has the pleasure to announce the release of the new version 1.1.0 of its popular MySQL, MariaDB and Percona Server multi-instance environment MyEnv.

The majority of improvements happened in the MySQL Backup Manager (mysql_bman) where we added a backup catalog.

You can download MyEnv from here.

In the inconceivable case that you find a bug in MyEnv please report it to our Bugtracker.

Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.

Upgrade from 1.0.5 to 1.1.0 # cd ${HOME}/product # tar xf /download/myenv-1.1.0.tar.gz # rm -f myenv # ln -s myenv-1.1.0 myenv

If you are using plug-ins for showMyEnvStatus create all the links in the new directory structure:

cd ${HOME}/product/myenv ln -s ../../utl/oem_agent.php plg/showMyEnvStatus/

Replace the following files:

• cp ${HOME}/product/myenv/etc/variables.conf.template /etc/myenv/variables.conf
• cp ${HOME}/product/myenv/bin/myenv.server /etc/init.d/myenv

Changes in MyEnv 1.1.0 MyEnv

• Error with !includedir fixed (Bug #143).
• tput is hidden in interactive mode now. No more nasty warning messages.
• Start/stop script did not pass error code correctly.
• Timezone complain on myenv_start_stop.php fixed with temporary fix.
• Init script should not through errors on SuSE any more.
• Init script is improved. Myenv should only start if network is available (runlevel).
• mysqladmin complains now if my.cnf has wrong parameters and does not show the schema down any more.
• MYSQL_HOME was changed from basedir to datadir, consider this for upgrade, this is a significant change, impact is not clear!
• Under some circumstances up did not show all schemata, fixed.

MyEnv Installer

• No changes.

MyEnv Utilities

• NUMA maps script from Jeremy Cole added.
• block_galera_node.sh fixed for more than 1 back-end.

MySQL Backup Manager

• For many backup types cleanup, archive and compress functionality added.
• Schema backup per-schema writes log pos now to log file and catalog.
• Binlog policy added.
• Backup structure is not created any more for cleanup and catalog operations.
• Binlog backup should work now with and without default location.
• Passing strange characters in password is handled more robust now.
• Schema names more robust with back-ticks.
• memory-table-check bug fixed.
• Command line is displayed in output (without exposing password).
• Cleanup of archivedir is possible now.
• Backup for configuration file implemented.
• Physical backup based on xtrabackup/mysqlbackup implemented.
• All exit's replaced by returns. Proper error handling should be possible.
• Backup logging implemented.
• Password from command line is not exposed any more to log file. Back-port from v1.0.5.
• Per schema privilege backup implemented.

MySQL Backup Manager Catalog

• Catalog creation and catalog upgrade integrated.

It is not clear for many MySQL users that Percona XtraDB Cluster (PXC) and MariaDB Galera Cluster depend on the same Galera library i.e used in Galera Cluster for MySQL which is provided by Codership team:

• Galera Cluster: MySQL Server (by Oracle) + Galera library.
• Percona XtraDB Cluster: Percona Server + Galera library.
• MariaDB Galera Cluster: MariaDB Server + Galera library.

But the question is, are there any performance differences between the three of them ?

Let's discover that by doing some simple benchmark to test MySQL write performance in Galera Cluster, PXC and MariaDB Galera Cluster installations.

System Information: HW configurations (AWS Servers): Nodes Servers HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 8, # of threads 16, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 120GB/ 5400RPM.

Load balancer Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2651 v2 @ 1.80GHz (# of cores 4, # of threads 8, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Load generator Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 16, # of threads 32, HT enabled).
• Memory: 32GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Software configurations:

• OS : Red Hat Enterprise Linux Server release 6.5 (Santiago)
• Sysbench : 0.5.3
• GLB : 1.0.0
• Galera Cluster : 5.5.34 and 5.6.16
• Percona XtraDB Cluster : 5.5.37 and 5.6.19
• MariaDB Galera Cluster : 5.5.38 and 10.0.12
• Galera Library : 3.5

Test Information:

• The testing environment consists of 5 AWS servers, three servers for a three-node cluster (each node is installed on a single server), one server for the load balancer and the final server for the load generator in which sysbench is installed to send requests to the load balancer from.
• Sysbench command: sysbench --num-threads=64 --max-requests=1000 --db-driver=mysql --test=/usr/share/doc/sysbench/tests/db/oltp.lua --mysql-table-engine=InnoDB --mysql-user=dev --mysql-password='test' --mysql-host=load_balancer_ip run .
• Table structure which was used by sysbench tests: mysql> show create table sbtest.sbtest\G CREATE TABLE `sbtest` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `k` int(10) unsigned NOT NULL DEFAULT '0', `c` char(120) NOT NULL DEFAULT '', `pad` char(60) NOT NULL DEFAULT '', PRIMARY KEY (`id`), KEY `k` (`k`) ) ENGINE=InnoDB AUTO_INCREMENT=8574 DEFAULT CHARSET=latin1
• The my.cnf used is something like: [mysqld] key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 innodb_buffer_pool_size = 8G innodb_flush_log_at_trx_commit = 0 expire_logs_days = 10 max_binlog_size = 100M server-id = 1 log-bin = mysql-bin binlog_format = ROW auto_increment_increment = 3 auto_increment_offset = 1 log_slave_updates default_storage_engine = InnoDB # Path to Galera library wsrep_provider = /usr/lib64/galera/libgalera_smm.so # Cluster connection URL contains the IPs of node#1, node#2 and node#3 wsrep_cluster_address = gcomm://nodeB-IP,nodeC-IP innodb_autoinc_lock_mode = 2 # Node #1 address wsrep_node_address = nodeA-IP # Cluster name wsrep_cluster_name = test_cluster # SST method wsrep_sst_method = rsync # Authentication for SST method wsrep_sst_auth = "sst:password"

Notes:

• The number of threads used in this test is 64 as it generated the highest throughput on all cluster installations.
• Each throughput value for each test case is generated by the average of ten (10) times execution.

Testing Results:

The raw results in Transactions / Sec might be useful:

sync_binlog=0innodb_flush_log_ at_trx_commitGalera Cluster 5.5.34PXC 5.5.37MariaDB Galera Cluster 5.5.38Galera Cluster 5.6.16PXC 5.6.15MariaDB Galera Cluster 10.0.120525.119534.022534.249519.575532.19520.7361125.615131.748341.384157.001162.783174.972526.761528.858524.039511.817526.06521.024sync_binlog=10242.201249.622262.516220.313229.807220.97196.82996.759148.815111.995114.8113.0562224.476210.904217.142209.139201.596214.311
Conclusion

According to the above results:

• innodb_flush_log_at_trx_commit = 1 significantly slows down Galera.
• sync_binlog also cuts in half the throughput.
• All other are more or less equal in throughput.

It is not clear for many MySQL users that Percona XtraDB Cluster (PXC) and MariaDB Galera Cluster depend on the same Galera library i.e used in Galera Cluster for MySQL which is provided by Codership team:

• Galera Cluster: MySQL Server (by Oracle) + Galera library.
• Percona XtraDB Cluster: Percona Server + Galera library.
• MariaDB Galera Cluster: MariaDB Server + Galera library.

But the question is, are there any performance differences between the three of them ?

Let's discover that by doing some simple benchmark to test MySQL write performance in Galera Cluster, PXC and MariaDB Galera Cluster installations.

System Information: HW configurations (AWS Servers): Nodes Servers HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 8, # of threads 16, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 120GB/ 5400RPM.

Load balancer Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2651 v2 @ 1.80GHz (# of cores 4, # of threads 8, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Load generator Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 16, # of threads 32, HT enabled).
• Memory: 32GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Software configurations:

• OS : Red Hat Enterprise Linux Server release 6.5 (Santiago)
• Sysbench : 0.5.3
• GLB : 1.0.0
• Galera Cluster : 5.5.34 and 5.6.16
• Percona XtraDB Cluster : 5.5.37 and 5.6.19
• MariaDB Galera Cluster : 5.5.38 and 10.0.12
• Galera Library : 3.5

Test Information:

• The testing environment consists of 5 AWS servers, three servers for a three-node cluster (each node is installed on a single server), one server for the load balancer and the final server for the load generator in which sysbench is installed to send requests to the load balancer from.
• Sysbench command: sysbench --num-threads=64 --max-requests=1000 --db-driver=mysql --test=/usr/share/doc/sysbench/tests/db/oltp.lua --mysql-table-engine=InnoDB --mysql-user=dev --mysql-password='test' --mysql-host=load_balancer_ip run .
• Table structure which was used by sysbench tests: mysql> show create table sbtest.sbtest\G CREATE TABLE `sbtest` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `k` int(10) unsigned NOT NULL DEFAULT '0', `c` char(120) NOT NULL DEFAULT '', `pad` char(60) NOT NULL DEFAULT '', PRIMARY KEY (`id`), KEY `k` (`k`) ) ENGINE=InnoDB AUTO_INCREMENT=8574 DEFAULT CHARSET=latin1
• The my.cnf used is something like: [mysqld] key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 innodb_buffer_pool_size = 8G innodb_flush_log_at_trx_commit = 0 expire_logs_days = 10 max_binlog_size = 100M server-id = 1 log-bin = mysql-bin binlog_format = ROW auto_increment_increment = 3 auto_increment_offset = 1 log_slave_updates default_storage_engine = InnoDB # Path to Galera library wsrep_provider = /usr/lib64/galera/libgalera_smm.so # Cluster connection URL contains the IPs of node#1, node#2 and node#3 wsrep_cluster_address = gcomm://nodeB-IP,nodeC-IP innodb_autoinc_lock_mode = 2 # Node #1 address wsrep_node_address = nodeA-IP # Cluster name wsrep_cluster_name = test_cluster # SST method wsrep_sst_method = rsync # Authentication for SST method wsrep_sst_auth = "sst:password"

Notes:

• The number of threads used in this test is 64 as it generated the highest throughput on all cluster installations.
• Each throughput value for each test case is generated by the average of ten (10) times execution.

Testing Results:

The raw results in Transactions / Sec might be useful:

sync_binlog=0innodb_flush_log_ at_trx_commitGalera Cluster 5.5.34PXC 5.5.37MariaDB Galera Cluster 5.5.38Galera Cluster 5.6.16PXC 5.6.15MariaDB Galera Cluster 10.0.120525.119534.022534.249519.575532.19520.7361125.615131.748341.384157.001162.783174.972526.761528.858524.039511.817526.06521.024sync_binlog=10242.201249.622262.516220.313229.807220.97196.82996.759148.815111.995114.8113.0562224.476210.904217.142209.139201.596214.311
Conclusion

According to the above results:

• innodb_flush_log_at_trx_commit = 1 significantly slows down Galera.
• sync_binlog also cuts in half the throughput.
• All other are more or less equal in throughput.

It is not clear for many MySQL users that Percona XtraDB Cluster (PXC) and MariaDB Galera Cluster depend on the same Galera library i.e used in Galera Cluster for MySQL which is provided by Codership team:

• Galera Cluster: MySQL Server (by Oracle) + Galera library.
• Percona XtraDB Cluster: Percona Server + Galera library.
• MariaDB Galera Cluster: MariaDB Server + Galera library.

But the question is, are there any performance differences between the three of them ?

Let's discover that by doing some simple benchmark to test MySQL write performance in Galera Cluster, PXC and MariaDB Galera Cluster installations.

System Information: HW configurations (AWS Servers): Nodes Servers HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 8, # of threads 16, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 120GB/ 5400RPM.

Load balancer Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2651 v2 @ 1.80GHz (# of cores 4, # of threads 8, HT enabled).
• Memory: 16GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Load generator Server HW configurations:

• CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz (# of cores 16, # of threads 32, HT enabled).
• Memory: 32GB RAM.
• Storage: HDD 10GB/ 5400RPM.

Software configurations:

• OS : Red Hat Enterprise Linux Server release 6.5 (Santiago)
• Sysbench : 0.5.3
• GLB : 1.0.0
• Galera Cluster : 5.5.34 and 5.6.16
• Percona XtraDB Cluster : 5.5.37 and 5.6.19
• MariaDB Galera Cluster : 5.5.38 and 10.0.12
• Galera Library : 3.5

Test Information:

• The testing environment consists of 5 AWS servers, three servers for a three-node cluster (each node is installed on a single server), one server for the load balancer and the final server for the load generator in which sysbench is installed to send requests to the load balancer from.
• Sysbench command: sysbench --num-threads=64 --max-requests=1000 --db-driver=mysql --test=/usr/share/doc/sysbench/tests/db/oltp.lua --mysql-table-engine=InnoDB --mysql-user=dev --mysql-password='test' --mysql-host=load_balancer_ip run .
• Table structure which was used by sysbench tests: mysql> show create table sbtest.sbtest\G CREATE TABLE `sbtest` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `k` int(10) unsigned NOT NULL DEFAULT '0', `c` char(120) NOT NULL DEFAULT '', `pad` char(60) NOT NULL DEFAULT '', PRIMARY KEY (`id`), KEY `k` (`k`) ) ENGINE=InnoDB AUTO_INCREMENT=8574 DEFAULT CHARSET=latin1
• The my.cnf used is something like: [mysqld] key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 innodb_buffer_pool_size = 8G innodb_flush_log_at_trx_commit = 0 expire_logs_days = 10 max_binlog_size = 100M server-id = 1 log-bin = mysql-bin binlog_format = ROW auto_increment_increment = 3 auto_increment_offset = 1 log_slave_updates default_storage_engine = InnoDB # Path to Galera library wsrep_provider = /usr/lib64/galera/libgalera_smm.so # Cluster connection URL contains the IPs of node#1, node#2 and node#3 wsrep_cluster_address = gcomm://nodeB-IP,nodeC-IP innodb_autoinc_lock_mode = 2 # Node #1 address wsrep_node_address = nodeA-IP # Cluster name wsrep_cluster_name = test_cluster # SST method wsrep_sst_method = rsync # Authentication for SST method wsrep_sst_auth = "sst:password"

Notes:

• The number of threads used in this test is 64 as it generated the highest throughput on all cluster installations.
• Each throughput value for each test case is generated by the average of ten (10) times execution.

Testing Results:

The raw results in Transactions / Sec might be useful:

sync_binlog=0innodb_flush_log_ at_trx_commitGalera Cluster 5.5.34PXC 5.5.37MariaDB Galera Cluster 5.5.38Galera Cluster 5.6.16PXC 5.6.15MariaDB Galera Cluster 10.0.120525.119534.022534.249519.575532.19520.7361125.615131.748341.384157.001162.783174.972526.761528.858524.039511.817526.06521.024sync_binlog=10242.201249.622262.516220.313229.807220.97196.82996.759148.815111.995114.8113.0562224.476210.904217.142209.139201.596214.311
Conclusion

According to the above results:

• innodb_flush_log_at_trx_commit = 1 significantly slows down Galera.
• sync_binlog also cuts in half the throughput.
• All other are more or less equal in throughput.

FromDual holds its annual company meeting this year in Barcelona, Spain.

We are pleased to invite everybody interested in MySQL technologies (MySQL, Galera Cluster, FromDual Tools, Percona Cluster, MariaDB, etc.) to participate on Thursday evening September 11 at the HCC MONTBLANC, Via Laietana 61, to meet, exchange ideas and discuss MySQL related topics.

The event starts at 18:00, we will meet in the hotel lobby. The planned schedule is:

• How to Implement GTID Replication in MySQL 5.6 (25') and 5' Questions and Answers.
• MySQL backup/restore for anonymized exports (25') and 5' Questions and Answers.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.

Please feel free to send us your suggestion about your presentation. Any technical or non-technical MySQL related topic is welcome. For example how you use MySQL in your company or special problems you have faced and solved (or not solved yet), research work you have done on MySQL products, business cases you solve with MySQL products, evaluations or experience you have made, etc. For the proposal please send us a mail.

Please also send us a short notice if you plan to participate or join us with MeetUp.

This gives us the possibility to arrange and organize all the infrastructure with the Hotel.

The event is free of costs for all participants.

We are pleased if you can make it to the event,
Your FromDual Team

FromDual holds its annual company meeting this year in Barcelona, Spain.

We are pleased to invite everybody interested in MySQL technologies (MySQL, Galera Cluster, FromDual Tools, Percona Cluster, MariaDB, etc.) to participate on Thursday evening September 11 at the HCC MONTBLANC, Via Laietana 61, to meet, exchange ideas and discuss MySQL related topics.

The event starts at 18:00, we will meet in the hotel lobby. The planned schedule is:

• How to Implement GTID Replication in MySQL 5.6 (25') and 5' Questions and Answers.
• MySQL backup/restore for anonymized exports (25') and 5' Questions and Answers.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.

Please feel free to send us your suggestion about your presentation. Any technical or non-technical MySQL related topic is welcome. For example how you use MySQL in your company or special problems you have faced and solved (or not solved yet), research work you have done on MySQL products, business cases you solve with MySQL products, evaluations or experience you have made, etc. For the proposal please send us a mail.

Please also send us a short notice if you plan to participate or join us with MeetUp.

This gives us the possibility to arrange and organize all the infrastructure with the Hotel.

The event is free of costs for all participants.

We are pleased if you can make it to the event,
Your FromDual Team

FromDual holds its annual company meeting this year in Barcelona, Spain.

We are pleased to invite everybody interested in MySQL technologies (MySQL, Galera Cluster, FromDual Tools, Percona Cluster, MariaDB, etc.) to participate on Thursday evening September 11 at the HCC MONTBLANC, Via Laietana 61, to meet, exchange ideas and discuss MySQL related topics.

The event starts at 18:00, we will meet in the hotel lobby. The planned schedule is:

• How to Implement GTID Replication in MySQL 5.6 (25') and 5' Questions and Answers.
• MySQL backup/restore for anonymized exports (25') and 5' Questions and Answers.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.
• Break 15 min
• Quick presentation (15') of YOUR project or company.
• Quick presentation (15') of YOUR project or company.

Please feel free to send us your suggestion about your presentation. Any technical or non-technical MySQL related topic is welcome. For example how you use MySQL in your company or special problems you have faced and solved (or not solved yet), research work you have done on MySQL products, business cases you solve with MySQL products, evaluations or experience you have made, etc. For the proposal please send us a mail.

Please also send us a short notice if you plan to participate or join us with MeetUp.

This gives us the possibility to arrange and organize all the infrastructure with the Hotel.

The event is free of costs for all participants.

We are pleased if you can make it to the event,
Your FromDual Team

FromDual tools provide valuable additional functionality which facilitate and optimize daily operations of your MySQL databases. Since our last newsletter a lot of things have changed in the FromDual tools.

To the MySQL Environment (MyEnv) numerous improvements and suggestions of our customers were added. The most important changes were introduced to the MySQL Backup Manager (mysql_bman).

With the MySQL Ops Center we meet the wishes of our numerous customers, which desire a graphical user interface for operating complex MySQL environments.
These users are often little used in handling MySQL but want nevertheless operate more complex MySQL installations as Master/Slave- or Master/Master-replications.

In the MySQL Performance Monitor (mpm) numerous little bugs have been fixed which were reported to us by our customers.

Note: In our MySQL Service Contracts, Business Hour (5x9) and All around the Clock (7x24) the usage and support of our tools is included.
If you would like to know more about our service prices, we are pleased to send you an offer.

MyEnv v1.0.5

The MySQL Environment (MyEnv) gets more and more popularity in the MySQL eco-system. MyEnv is optimized for MySQL and mimics the popular TVD BasEnv which is popular with bigger Oracle database users.

With MyEnv you can easily consolidate several MySQL instances (mysqld) on one single machine. Thanks to MyEnv this complicated configuration is a piece of cake. Furthermore MyEnv is more and more common with customers testing their applications against different MySQL versions (5.5, 5.6 and 5.7) or different MySQL branches (Galera Cluster, MariaDB, Percona Server).

The most important improvements in MyEnv v1.0.5 are:

• Old PHP functions were replaced to achieve better compatibility with PHP 5.4 and 5.5.
• MyEnv overview (up) of installed MySQL instances was polished and numerous smaller bugs were fixed.
• Extensions for active/passive fail-over clusters and Oracle Enterprise Monitor Agents for MySQL were integrated.
• The user guidance of the MyEnv installer was made more user friendly.
• Problems of MyEnv with SuSE Linux Enterprise Server (SLES) were removed.
• The tools for MySQL Partitions were extended and improved.

All improvements in detail you can find in the Release Notes.

Here you can download MyEnv.

MySQL Backup Manager v1.0.5

The MySQL Backup Manager (mysql_bman) is actually getting most of interest from our customers. It significantly eases backups for MySQL for all different types of backups.

At this point we would like to quote a MySQL user:

"MySQL Backup Manager is a very nice tool! Congratulations for FromDual! I made my own shell script for catalog and maintained backups by xtrabackup, but mysql_bman is the best! Xtrabackup + mysql_bman!!!"

In mysql_bman version v1.0.5 the following improvements were integrated:

• Security improvements (password is not exposed any more).
• Every instance can be tagged with a name and uniquely identified.
• The MySQL Backup Manager considers now the MySQL configuration file ~/.my.cnf.
• The compression of backups can be disabled to support de-duplicating drives.
• The option --no-memory-table-check was introduced to allow inconsistent backups with MEMORY tables.

Download (included in MyEnv).

MySQL Ops Center v0.2

Our MySQL customers have requested a simple user interface to operate and administer many MySQL databases. This is the reason why FromDual has launched the MySQL Ops Center.
The Ops Center can centrally operate and control complex MySQL configurations like Master/Slave or Master/Master set-ups, monitor, start, stop and reconfigure the replication.
With the MySQL Ops Center you can also start and stop easily virtual IP's and move them to an other host.

The most important features, which were added to the first public preview-release of the MySQL Ops Center v0.2. are:

• Starting and stopping of MySQL databases on remote machines by a central management console.
• Starting and stopping of the MySQL replication.
• Starting and stopping of a virtual IP (VIP).
• Fail-over of VIP from active master to slave (master/slave replication) or passive master (master/master replication).
• Configuration of the master/slave replication.

The MySQL Ops Center can be downloaded here. Further information you can find at MySQL Ops Center.

MySQL Performance Monitor v0.9.3

The MySQL Performance Monitor (mpm) was optimized in many places. Further know bugs were fixed and the mpm agent was made ready for the newest Zabbix version v2.2:

• Bugs related to sha/sha1 encryption were fixed.
• A stopped database is better detected now.
• DRBD informations were improved.
• New behaviour of zabbix_senders in Zabbix v2.2 is handled correctly now.
• New measuring points was added (Galera Cluster) and wrong ones fixed.

You can download the latest version of MySQL Performance Monitor from here here and for more information about the manual installation just follow up the steps on the installation guide. To check all changes and improvements of MySQL Performance Monitor check out the Release Notes.

Taxonomy upgrade extras: galeraBackupmanagermonitoringOperationsMyEnvfromdual_brman

FromDual tools provide valuable additional functionality which facilitate and optimize daily operations of your MySQL databases. Since our last newsletter a lot of things have changed in the FromDual tools.

To the MySQL Environment (MyEnv) numerous improvements and suggestions of our customers were added. The most important changes were introduced to the MySQL Backup Manager (mysql_bman).

With the MySQL Ops Center we meet the wishes of our numerous customers, which desire a graphical user interface for operating complex MySQL environments.
These users are often little used in handling MySQL but want nevertheless operate more complex MySQL installations as Master/Slave- or Master/Master-replications.

In the MySQL Performance Monitor (mpm) numerous little bugs have been fixed which were reported to us by our customers.

Note: In our MySQL Service Contracts, Business Hour (5x9) and All around the Clock (7x24) the usage and support of our tools is included.
If you would like to know more about our service prices, we are pleased to send you an offer.

MyEnv v1.0.5

The MySQL Environment (MyEnv) gets more and more popularity in the MySQL eco-system. MyEnv is optimized for MySQL and mimics the popular TVD BasEnv which is popular with bigger Oracle database users.

With MyEnv you can easily consolidate several MySQL instances (mysqld) on one single machine. Thanks to MyEnv this complicated configuration is a piece of cake. Furthermore MyEnv is more and more common with customers testing their applications against different MySQL versions (5.5, 5.6 and 5.7) or different MySQL branches (Galera Cluster, MariaDB, Percona Server).

The most important improvements in MyEnv v1.0.5 are:

• Old PHP functions were replaced to achieve better compatibility with PHP 5.4 and 5.5.
• MyEnv overview (up) of installed MySQL instances was polished and numerous smaller bugs were fixed.
• Extensions for active/passive fail-over clusters and Oracle Enterprise Monitor Agents for MySQL were integrated.
• The user guidance of the MyEnv installer was made more user friendly.
• Problems of MyEnv with SuSE Linux Enterprise Server (SLES) were removed.
• The tools for MySQL Partitions were extended and improved.

All improvements in detail you can find in the Release Notes.

Here you can download MyEnv.

MySQL Backup Manager v1.0.5

The MySQL Backup Manager (mysql_bman) is actually getting most of interest from our customers. It significantly eases backups for MySQL for all different types of backups.

At this point we would like to quote a MySQL user:

"MySQL Backup Manager is a very nice tool! Congratulations for FromDual! I made my own shell script for catalog and maintained backups by xtrabackup, but mysql_bman is the best! Xtrabackup + mysql_bman!!!"

In mysql_bman version v1.0.5 the following improvements were integrated:

• Security improvements (password is not exposed any more).
• Every instance can be tagged with a name and uniquely identified.
• The MySQL Backup Manager considers now the MySQL configuration file ~/.my.cnf.
• The compression of backups can be disabled to support de-duplicating drives.
• The option --no-memory-table-check was introduced to allow inconsistent backups with MEMORY tables.

Download (included in MyEnv).

MySQL Ops Center v0.2

Our MySQL customers have requested a simple user interface to operate and administer many MySQL databases. This is the reason why FromDual has launched the MySQL Ops Center.
The Ops Center can centrally operate and control complex MySQL configurations like Master/Slave or Master/Master set-ups, monitor, start, stop and reconfigure the replication.
With the MySQL Ops Center you can also start and stop easily virtual IP's and move them to an other host.

The most important features, which were added to the first public preview-release of the MySQL Ops Center v0.2. are:

• Starting and stopping of MySQL databases on remote machines by a central management console.
• Starting and stopping of the MySQL replication.
• Starting and stopping of a virtual IP (VIP).
• Fail-over of VIP from active master to slave (master/slave replication) or passive master (master/master replication).
• Configuration of the master/slave replication.

The MySQL Ops Center can be downloaded here. Further information you can find at MySQL Ops Center.

MySQL Performance Monitor v0.9.3

The MySQL Performance Monitor (mpm) was optimized in many places. Further know bugs were fixed and the mpm agent was made ready for the newest Zabbix version v2.2:

• Bugs related to sha/sha1 encryption were fixed.
• A stopped database is better detected now.
• DRBD informations were improved.
• New behaviour of zabbix_senders in Zabbix v2.2 is handled correctly now.
• New measuring points was added (Galera Cluster) and wrong ones fixed.

You can download the latest version of MySQL Performance Monitor from here here and for more information about the manual installation just follow up the steps on the installation guide. To check all changes and improvements of MySQL Performance Monitor check out the Release Notes.

Taxonomy upgrade extras: galeraBackupmanagermonitoringOperationsMyEnvfromdual_brman