Mysql features for the enterprise

MySQLFeatures for the enterprise

Giuseppe MaxiaQA Director

Continuent, Inc

This work is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Wednesday, December 1, 2010

about me - Giuseppe Maxia

• a.k.a. The Data Charmer• QA Director at Continuent, Inc• Long time hacking with MySQL features• Formerly, MySQL community manager, database

consultant, designer, coder.• A passion for QA, open source, and community• Blogger

•http://datacharmer.blogspot.com

Contents• Refresh of MySQL main features

• Future: MySQL 5.5✦ performance (InnoDB default engine,

Performance schema)✦ ease of use (partitioning, SIGNAL)✦ reliability (semisynch replication)

• Current: MySQL 5.1✦ performance: InnoDB plugin 1.0.13

Main features• Ease of use

• Installation

• Maintenance

• Reliability

• ACID compliant

• Built-in replication

• Performance

• Scalable

• Built-in partitioning

And more ...• Stored routines

• Triggers

• Views

• Information and performance schema

• Event scheduler

• Pluggable functions

• Pluggable storage engines

Installation

As easy as• apt-get install mysql-server

• yum install mysql-server

Manual installation requires less than 15 minutes

MVCC storage engine

• Use Innodb

• Transactions

• Referential integrity

Replication principles

a simple web application

scheme

database server

web server

clients

r/w requests

database server

web servers

load balancer

clients

r/w requests

scaling web requests

writeread

database load on a simple

web application

85% 15%

readwrite

database load on a successful web

application

20% 80%

database server

web servers

load balancer

clients

r/w requests✘

scaling up means buying

a bigger database

server

readwrite

the bigger database server will eventually

have the same problem

80%20%

read/writemaster

read/onlyslaves

web servers

load balancer

clients

a web application

scheme with replication

read/writemaster

read/onlyslaves

readwriteread

database load with

replication

85% 15% 100%

read/writemaster

read/onlyslaves

readwriteread

scaling database load

with replication

85% 15% 100%

Replication assessmentwithout replication with replication

database handling

performance

Point in Time recovery

failover

write scaling

backup

read scaling

easy harder

high lower (binary logs)

none easy

none possible

none minimal

with downtime without downtime

none easy

Partitioning

Remember the MERGE tables?separate tablesrisk of duplicatesinsert in each tableno constraints

MERGE TABLE

It isn't a merge table!One tableNo risk of duplicatesinsert in one tableconstraints enforced

PARTITIONED TABLE

Partition pruning 1a - unpartitioned table - SINGLE RECORD

select * from table_name where colx = 120

Partition pruning 1a - unpartitioned table - SINGLE RECORD

Partition pruning 1c - unpartitioned table - RANGE

select * from table_name where colx between 120 and 230

Partition pruning 2a - table partitioned by colx - SINGLE REC

100-199

200-299

300-399

400-499

500-599

Partition pruning 2a - table partitioned by colx - SINGLE REC

DATA I

100-199

200-299

300-399

400-499

500-599

Partition pruning 2b - table partitioned by colx - SINGLE REC

100-199

200-299

300-399

400-499

500-599

Partition pruning 2c - table partitioned by colx - RANGE

100-199

200-299

300-399

400-499

500-599

select * from table_name where colx between 120 and 230

Benchmarking results (huge server)engine 6 month rangeInnoDB 4 min 30sMyISAM 25.03sArchive 22 min 25sInnoDB partitioned by month 13.19MyISAM partitioned by year 6.31MyISAM partitioned by month 4.45Archive partitioned by year 16.67Archive partitioned by month 8.97

Leveraging replication

read/writemaster

read/onlyslaves

R/WR/O

load balancer

load balancing

backup master

slaves

STOP SLAVE

remove slave from load balancer

START SLAVE

perform backup

attach slave to load

balancer

Let slave catch up

master

slaves

STOP SLAVE

remove slave from load balancer

START SLAVE

calculate summary

tables

attach slave to load

balancer

Let slave catch up

makesummary

tables

master

innodbnon partitioned

innodbnon partitionedinnodb

partitioned by range

MyISAMpartitioned by range

Partitionsfor heavy statistics

master

innodbnon partitioned

ARCHIVEpartitioned by range

(date)

(product)

(location)

Simulating multiple

dimensions

MySQL 5.5

• MySQL 5.5.7-rc released in November

• MySQL 5.5.x-GA coming in December

• Default storage engine is now InnoDB

• Lots of goodies

• Future: MySQL 5.5✦ performance (InnoDB default

engine, Performance schema)✦ ease of use (partitioning, SIGNAL)✦ reliability (semisynch replication)

default engineselect @@version,@@storage_engine;+-----------+------------------+| @@version | @@storage_engine |+-----------+------------------+| 5.1.52 | MyISAM |+-----------+------------------+

select @@version, @@storage_engine;+-----------+------------------+| @@version | @@storage_engine |+-----------+------------------+| 5.5.7-rc | InnoDB |+-----------+------------------+

Plugin versionselect @@version, @@innodb_version;+-----------+------------------+| @@version | @@innodb_version |+-----------+------------------+| 5.5.7-rc | 1.1.3 |+-----------+------------------+

InnoDB at a glance

• Performance Improvements✦ Improved recovery performance✦ Multiple buffer pool instances✦ Multiple rollback segments✦ Native asynchronous I/O for Linux✦ Extended change buffering

Faster!

• How fast?

• In my benchmarks, 10% to 50% faster.

• Others have reported much higher gains.

• You decide.

• Test it under your load.

PERFORMANCE SCHEMA

• PERFORMANCE_SCHEMA presents low level MySQL performance information

• Data can be cleared

• Filters with WHERE are allowed

• Must be enabled with --performance_schema

performance schemaSELECT EVENT_ID, EVENT_NAME, TIMER_WAITFROM EVENTS_WAITS_HISTORY WHERE THREAD_ID = 13ORDER BY EVENT_ID;+----------+-----------------------------------------+------------+| EVENT_ID | EVENT_NAME | TIMER_WAIT |+----------+-----------------------------------------+------------+| 86 | wait/synch/mutex/mysys/THR_LOCK::mutex | 686322 || 87 | wait/synch/mutex/mysys/THR_LOCK_malloc | 320535 || 88 | wait/synch/mutex/mysys/THR_LOCK_malloc | 339390 || 89 | wait/synch/mutex/mysys/THR_LOCK_malloc | 377100 || 90 | wait/synch/mutex/sql/LOCK_plugin | 614673 || 91 | wait/synch/mutex/sql/LOCK_open | 659925 || 92 | wait/synch/mutex/sql/THD::LOCK_thd_data | 494001 || 93 | wait/synch/mutex/mysys/THR_LOCK_malloc | 222489 || 94 | wait/synch/mutex/mysys/THR_LOCK_malloc | 214947 || 95 | wait/synch/mutex/mysys/LOCK_alarm | 312993 |+----------+-----------------------------------------+------------+

performance schemamysql> UPDATE SETUP_INSTRUMENTS SET ENABLED = 'NO' WHERE NAME = 'wait/synch/mutex/myisammrg/MYRG_INFO::mutex';

mysql> UPDATE SETUP_CONSUMERS SET ENABLED = 'NO' WHERE NAME = 'file_summary_by_instance';

MySQL 5.5 enhancements• PARTITION BY RANGE COLUMNS• PARTITION BY LIST COLUMNS• TO_SECONDS

MySQL 5.5 enhancements

CREATE TABLE t ( dt date)PARTITION BY RANGE (TO_DAYS(dt))( PARTITION p01 VALUES LESS THAN (TO_DAYS('2007-01-01')), PARTITION p02 VALUES LESS THAN (TO_DAYS('2008-01-01')), PARTITION p03 VALUES LESS THAN (TO_DAYS('2009-01-01')), PARTITION p04 VALUES LESS THAN (MAXVALUE));

BEFORE

SHOW CREATE TABLE t \G Table: tCreate Table: CREATE TABLE `t` ( `dt` date DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1/*!50100 PARTITION BY RANGE (TO_DAYS(dt))(PARTITION p01 VALUES LESS THAN (733042) ENGINE = MyISAM,[…]

BEFORE

CREATE TABLE t ( dt date)PARTITION BY RANGE COLUMNS (dt)( PARTITION p01 VALUES LESS THAN ('2007-01-01'), PARTITION p02 VALUES LESS THAN ('2008-01-01'), PARTITION p03 VALUES LESS THAN ('2009-01-01'), PARTITION p04 VALUES LESS THAN (MAXVALUE));

AFTER5.5

SHOW CREATE TABLE t Table: tCreate Table: CREATE TABLE `t` ( `dt` date DEFAULT NULL) ENGINE=MyISAM DEFAULT CHARSET=latin1/*!50500 PARTITION BY RANGE COLUMNS(dt)(PARTITION p01 VALUES LESS THAN ('2007-01-01') ENGINE = MyISAM,[…]

AFTER5.5

MySQL 5.5 - Multiple columns

CREATE TABLE t ( a int, b int)PARTITION BY RANGE COLUMNS (a,b)( PARTITION p01 VALUES LESS THAN (10,1), PARTITION p02 VALUES LESS THAN (10,10), PARTITION p03 VALUES LESS THAN (10,20), PARTITION p04 VALUES LESS THAN (MAXVALUE, MAXVALUE));

CREATE TABLE employees ( emp_no int(11) NOT NULL, birth_date date NOT NULL, first_name varchar(14) NOT NULL, last_name varchar(16) NOT NULL, gender char(1) DEFAULT NULL, hire_date date NOT NULL) ENGINE=MyISAMPARTITION BY RANGE COLUMNS(gender,hire_date)(PARTITION p01 VALUES LESS THAN ('F','1990-01-01'), PARTITION p02 VALUES LESS THAN ('F','2000-01-01'), PARTITION p03 VALUES LESS THAN ('F',MAXVALUE), PARTITION p04 VALUES LESS THAN ('M','1990-01-01'), PARTITION p05 VALUES LESS THAN ('M','2000-01-01'), PARTITION p06 VALUES LESS THAN ('M',MAXVALUE), PARTITION p07 VALUES LESS THAN (MAXVALUE,MAXVALUE)

MySQL 5.5 enhancements• TRUNCATE PARTITION• TO_SECONDS()

SIGNAL and RESIGNAL

• Allow error handling in stored routines

• The execution is passed to an error handler

• Accessible error values are SQLSTATE, MESSAGE_TEXT and MYSQL_ERRNO

• RESIGNAL can pass along the original or a new information

semi-synchronous replication

master

slave 1 slave 2

semisynch master plugin

semisynch slave plugin

master

slave 1 slave 2

COMMIT

client

master

slave 1 slave 2

client

binary logCOMMIT

master

slave 1 slave 2

client

binary logCOMMIT

relay log

master

slave 1 slave 2

client

binary logCOMMIT

relay log

confirm log reception

master

slave 1 slave 2

client

binary logCOMMIT

relay log

Missed announcement

• A GA release

• As of MySQL 5.1.47

• The InnoDB plugin is GA

• Ready to use for immediate gains

INNODB

13Wednesday, December 1, 2010

INNODB

INFORMATION SCHEMA table plugin

MySQL Server

InnoDB plugin

Installation (1)my.cnf

[mysqld]plugin_dir = /usr/local/mysql/lib/pluginignore_builtin_innodbplugin-load=innodb=ha_innodb_plugin.sodefault-storage-engine=InnoDBinnodb_file_per_table=1innodb_file_format=barracudainnodb_strict_mode=1

Installation (1a)my.cnf

[mysqld]plugin-load=innodb=ha_innodb_plugin.so;innodb_trx=ha_innodb_plugin.so;innodb_locks=ha_innodb_plugin.so;innodb_lock_waits=ha_innodb_plugin.so;innodb_cmp=ha_innodb_plugin.so;innodb_cmp_reset=ha_innodb_plugin.so;innodb_cmpmem=ha_innodb_plugin.so;innodb_cmpmem_reset=ha_innodb_plugin.so#(all in one line with no spaces)

Installation (2)SET GLOBAL innodb_fast_shutdown=0;

RESTART the server

Installation - 2nd method (1)my.cnf

[mysqld]ignore_builtin_innodb

Installation - 2nd method (2)SET GLOBAL innodb_fast_shutdown=0;

RESTART the server

Installation - 2nd method (3)mysqlINSTALL PLUGIN INNODB SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_TRX SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_LOCKS SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_LOCK_WAITS SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_CMP SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_CMP_RESET SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_CMPMEM SONAME 'ha_innodb_plugin.so';INSTALL PLUGIN INNODB_CMPMEM_RESET SONAME 'ha_innodb_plugin.so';

Installation - 2nd method (4)my.cnf

[mysqld]

default-storage-engine=InnoDBinnodb_file_per_table=1innodb_file_format=barracudainnodb_strict_mode=1

Installation - 2nd method (5)SET GLOBAL innodb_fast_shutdown=0;

RESTART the server

Installation differences• Method 1 (plugin-load in my.cnf)

✦ Only one operation✦ But error prone (one looooong command)✦ plugins not stored in mysql.plugin table

• Method 2 (install plugin) ✦ plugin info saved to mysql.plugin table✦ Easier to write✦ 2 restarts required

CAVEAT

• If you uninstall the InnoDB plugin, remember:✦ The tables are not backward compatible✦ You must uninstall all the

INFORMATION_SCHEMA plugin tables BEFORE removing the InnoDB plugin

✦ If the plugin is busy, it may not be removed until you restart the server

hands on

Checking installationselect @@version, @@innodb_version;+-----------+------------------+| @@version | @@innodb_version |+-----------+------------------+| 5.1.52 | 1.0.13 |+-----------+------------------+

Detecting lockssession1> select c from t1 for update;+------+| c |+------+| aaa || bbb || ccc |+------+

Detecting lockssession2> select c from t1 for update;

[… waiting]

Detecting lockssession3> select i from t1 for update;

[… waiting]

getting locks informationSELECT r.trx_id waiting_trx_id, r.trx_mysql_thread_id waiting_thread, r.trx_query waiting_query, b.trx_id blocking_trx_id, b.trx_mysql_thread_id blocking_thread, b.trx_query blocking_query FROM innodb_lock_waits w INNER JOIN innodb_trx b ON b.trx_id = w.blocking_trx_id INNER JOIN innodb_trx r ON r.trx_id = w.requesting_trx_id

getting locks information

getting locks information************* 1. row ************** waiting_trx_id: 711 waiting_thread: 3 waiting_query: select c from t1 for updateblocking_trx_id: 710blocking_thread: 2 blocking_query: select i from t1 for update

getting locks information************* 2. row ************** waiting_trx_id: 711 waiting_thread: 3 waiting_query: select c from t1 for updateblocking_trx_id: 70Fblocking_thread: 1 blocking_query: NULL

getting locks information************* 3. row ************** waiting_trx_id: 710 waiting_thread: 2 waiting_query: select i from t1 for updateblocking_trx_id: 70Fblocking_thread: 1 blocking_query: NULL

Mysql features for the enterprise

Technology

MySQL ENTERPRISE EDITION · PDF fileORACLE DATA SHEET 3 • MySQL Enterprise Firewall MySQL Enterprise Firewall blocks SQL Injection attacks that can result in loss of valuable personal

MySQL Features & Implementation

MySQL ENTERPRISE EDITION · MySQL Enterprise Edition reduces the risk, cost, and complexity in developing, deploying, and managing business-critical MySQL applications. Only MySQL

Extending MySQL Enterprise Monitor

MySQL Enterprise Backup User's Guide (Version 3.5.4) · MySQL Enterprise Backup User's Guide (Version 3.5.4) Abstract This is the User's Guide for the MySQL Enterprise Backup product,

MySQL Enterprise Backup (MEB)

MySQL Enterprise Monitor 3.4.8 Manual · This manual documents MySQL Enterprise Monitor version 3.4.8. For notes detailing the changes in each release, see the MySQL Enterprise Monitor

MySQL Enterprise Monitor 2 · MySQL Enterprise Monitor 2.2 iv 4.1 Creating Advisors and Rules ..... 93

Mysql User Camp : 20th June - Mysql New Features

MySQL Enterprise Monitor 3.0.27 Manual3.3.3 Users Created on First Log-in..... 24 4 Service Manager Installation ..... 25 4.1 MySQL Enterprise Monitor Installation 4.2 MySQL Enterprise

MySQL Enterprise Monitor 4.0.12 ManualAbstract This manual documents MySQL Enterprise Monitor version 4.0.12. For notes detailing the changes in each release, see the MySQL Enterprise

MySQL WhitePaper New Features in MySQL Cluster 51

MySQL Enterprise Backup

MySQL enterprise backup overview

A Comparison of PostgreSQL 9.0 and MySQL 5info.enterprisedb.com/...Plus...MySQL_5.5_20110627.pdf · Core Database Features PostgreSQL Postgres Plus Adv. Server MySQL 5.5 Enterprise

MySQL Day Paris 2016 - MySQL Enterprise Edition

MySQL ENTERPRISE EDITION · MySQL ENTERPRISE EDITION ... and Windows Active Directory. MySQL Enterprise Authentication enables organizations to implement a Single Sign …

MySQL Enterprise Monitor 2 - Oracle · MySQL Enterprise Monitor 2.2 Manual Abstract This manual documents the MySQL Enterprise Monitor version 2.2. Document generated on: 2010-11-03

MySQL Performance Tuning - koenig-solutions.com€¦ · MySQL Enterprise Monitor: Architecture 3 -15 MySQL Enterprise Monitor: Query Analyzer 3 -16 MySQL Enterprise Monitor: Dashboard

MySQL Enterprise Edition WP - techxtend.ca · Title: MySQL Enterprise Edition WP Author: MySQL Product Management Created Date: 20120918162445Z