oli's blog

Im Admin-Magazin 2011/06 hat es einen netten Artikel über MySQL und PostgreSQL Performance Tuning: Duell der Datenbanken: In einem Shootout messen sich MySQL und PostgreSQL

Hello Vineet,

Great if it was a help for you…

Angemeldet haben sich: Volker, Erkan, Mario, Oli, Ronny, (Norbert), …

Hallo zusammen,

Einige von Euch haben sicher vor, an die DOAG Conference 2011 nach Nürnberg zu kommen, welche vom 15. bis 17. November statt findet.

Michal Hrušecký did a Survey of the usage of different MySQL branches on OpenSuSE Linux. The results can be found in his article: MySQL survey results (Oct 17, 2011).

We have seen a customer running a MySQL instance with about 1 Mio InnoDB tables. He had some problems (hick-ups) but basically it worked…

This depends a bit on version and distribution. Debian/Ubuntu for example sets bind-address to localhost/127.0.0.1 afaik.

Hello BBlue,

Can you please elaborate a bit more what the problem is? It is not clear to me where you stuck.

Galera features

Galera provides the following features:

• Synchronous replication
• Active/active multi-master topology
• Read and write to any cluster node
• Automatic membership control, failed nodes drop from the cluster
• Automatic node joining
• True parallel row level replication
• Direct client connections
• Drop-in replacement for native MySQL

Galera benefits

Benefits using Galera Replication:

Table of Contents

• Reasons to Upgrade MariaDB or MySQL
• How to Upgrade to MariaDB or MySQL
• MariaDB and MySQL Reserved Keywords
• MariaDB and MySQL Problems we hit in real life
  • Upgrade MySQL 4.1 to MySQL 5.1
  • Upgrade MySQL 4.1 to MySQL 5.6
  • Upgrade MySQL 5.0 to MySQL 5.1
  • Upgrade MySQL 5.0 to MySQL 5.6
  • Upgrade MySQL 5.0 to MariaDB 10.3
  • Upgrade MySQL 5.1 to MySQL 5.5
  • Upgrade MySQL 5.5 to MySQL 5.6
  • Upgrade MySQL 5.6 to MySQL 5.7
  • Upgrade MySQL 5.7.12 to MySQL 5.7.21
  • Upgrade MySQL 5.7 to MySQL 8.0
  • Upgrade MariaDB 5.5 to MariaDB 10.5
  • Upgrade MariaDB 10.2 to MariaDB 10.3
  • Upgrade MariaDB 10.2 to MariaDB 10.4
  • Upgrade MariaDB 10.2 to MariaDB 10.5
  • Upgrade MariaDB 10.3 to MariaDB 10.5
  • Upgrade MariaDB 10.3 to MariaDB 10.6
  • Upgrade MariaDB 10.4 to MariaDB 10.5
  • Upgrade MariaDB 10.5 to MariaDB 10.6
  • Upgrade MariaDB 10.11 to MariaDB 11.4
  • Upgrade MariaDB 11.4 to MariaDB 11.8
• Migration between MySQL, MariaDB and Percona Server
• Migration from MyISAM to InnoDB
• Migration from MyISAM to Aria
• Switching from Statement Based Replication (SBR) to Row Based Replication (RBR)
• Switching from non-partitioned to partitioned tables
• Switching from MariaDB or MySQL to Galera
• Convert from latin1 Character Set to utf8mb4 Character Set

Downgrading between Major Versions of MariaDB and Downgrading MySQL (for 5.7 and older).

With a partner we are planning and Advanced MySQL DBA workshop. As the name says it should be a workshop. Its planned duration is 2 days. So within 2 days we can cover 4 to 8 topics more deeply. Requirements: VirtualBox, VMware, own Laptop?

Workshop topics

Duration: 3 days, Exercises

• Partitioning
  • Partitioning by time (temporal data)
  • Optimizer and Partitioning
  • Limitations
  • New 5.5 and 5.6 features of Partitioning
• InnoDB Architecture
  • Clustered PK
  • InnoDB Internals
  • InnoDB Online features
  • New Performance Features in 5.5 and 5.6
  • Operations of InnoDB
• Performance Tuning and Benchmarking
  • Basics, Latency and Throughput
  • Profiling
  • Benchmarking
  • Benchmarking Tools
• Memcached
  • Caching strategies
  • Operations
  • ding
• HA and replication solutions
  • Replication
  • Scale-Out
  • DRBD
• Blob streaming engine
• Handler Socket and Memcached-API

Hi Partha Dutta,

What you are describing is mentioned in Literature reference [3].

Hi Baron,

90% of the MySQL installations have 1 or 2 concurrent running queries. And most of the MySQL users do not have the time or the capabilities to tune queries, applications or add indexes.

After further investigations with MariaDB developers we found out, that the Problem can be solved when an explicit BEGIN or START TRANSACTION is set in front of the SELECT.

It looks really evil as you said. I could reproduce it with the following sequence:

Hi luke,

Great! Thank you for the hint. I somehow missed this bug… :(

It was just a complex Join Query as far as I can remember:

MySQL 5.6

The focus of this release seems to be on Replication, Partitioning and InnoDB/Performance.

In our opinion remote Consulting is non optimal for the customer because tight interaction is difficult remotely.