SkySQL Cloud MySQL MariaDB

SkySQLMeetup La Mutinerie / Paris12 / 12 / 12

SkySQL Ab 2012 Confidential

SkySQLSerge Frezefond

SkySQL Ab 2012 Confidential2

Content

MySQL – Product and Company

Introduction SkySQL

Company Structure

SkySQL Data Suite

SkySQL Enterprise Data Suite

SkySQL Cloud Data Suite

MariaDB


• MySQL

–#1 Open Source DBMS Worldwide

–50K downloads per day since 2003

–+13M active installations

• MySQL AB

–Founded by Monty Widenius & David Axmark

–My (pronounced Muu) is Monty's daugther

3

The MySQL AB Story


MySQL Founders turned SkySQL InvestorsThe shirts however are still as bad ...


MySQL AB

Founded 1995

2007 : $100M. Preparation for IPO - Nasdaq

Jan 2008 : Bought by Sun for $1B

May 2009 : Sun bought by Oracle for $6B

European Commission Enquiry

– DBMS Competition

Oracle made some promises

Green light just in time for Xmas 2009


The Oracle promises to the EU

6

• Continued Availability of Storage Engine APIs

• Non-assertion against any 3rd party or vendor for the implementation of storage engines under GPL

• Same licence commitment for commercial customers

• All MySQL® improvement licenses under the GPL

• Non-mandatory support

• Increased R&D

• MySQL® Customer Advisory Board

• MySQL® Storage Engine Advisory Board

• MySQL® Reference Manual

• Maintain customer’s choice to buy yearly support


The employees are ex-MySQL (actually >90%)

The founders are ex-MySQL executives The investors include the original founders of MySQL

Under Oracle's stewardship, a lot of MySQL customers are facing reduced service levels, price rises & vendor lock-in

We offer 24/7 worldwide MySQL & MariaDB support, consulting & training for MySQL as well as products designed to better deploy MySQL in the Cloud

– 85% of our revenues come from 24/7, 30-min-SLA support contracts

Operational since October 2010, we have over 350 customers incl. Amadeus, Deutsche Börse, Deutsche Telekom, Juniper Networks, Pitney Bowes, Time Warner, Virgin Mobile & Vodafone

SkySQL in 60 Seconds



CEO - Patrik Sallner - Cloud & SaaS specialist (previously Nokia & F-Secure)

CTO - Ivan Zoratti - Ex. Dir. Field Services EMEA @ MySQL AB

EVP Product Man. - Kaj Arnö – Ex VP Engineering & VP Community MySQL AB

VP Support - Dean Ellis – Ex Director WW Support MySQL AB VP Sales - Michael Carney – Ex. SEUR Sales Manager @ MySQL AB VP Sales EMEA - Magnus Stenberg – Ex. NEUR Sales Manager @ MySQL AB

Engineering - Monty Program ~20 MySQL developers (including 8 of the 10 key core

developers) lead by Monty Widenius (MySQL founder)

SkySQL Group (currently ~70 people worldwide)


SkySQL is the alternative to Oracle

10


SkySQL – Partner Eco-system

L3 Support Contracts

NRE Deals

End

Customer

L3 Support

Corrections

Hot Fixes

Monitoring

Consulting

Training

Corrections

POs

Contracts

Support Tickets

PR

SkySQL 24/7 WW SupportSkySQL 24/7 WW Support

L1, L2, L3 Support

Corrections

Hot Fixes

L1, L2, L3 Support

Contracts and NRE Deals

MHAMHA

Included in Advanced subscriptionIncluded in Advanced subscription


SkySQL Data Suite

12


SkySQL Enterprise Data Suite

13


SkySQL Enterprise – HA Solutions

16


SkySQL Cloud Data Suite

17


What is MariaDB?

A branch of MySQL– MariaDB is a backward compatible, drop-in

replacement for the MySQL Database Server

Open Source– The source code for MariaDB is publicly available

from Launchpad

– All code in MariaDB is open source

– No closed source modules

– Open bugs database


A Brief History

1983 - First version of what would become MySQL created by Monty Widenius

1995 – MySQL AB founded

1999 Jul – MySQL 3.23. alpha released

2000 – InnoDB released as part of MySQL-max

2001 Jan – MySQL 3.23 GA

2003 Mar – MySQL 4.0 GA

2004 Oct – MySQL 4.1 GA

2005 Oct – Oracle acquires InnoDB (Innobase)

2005 Oct – MySQL 5.0 GA


A Brief History

• 2005 Nov – Pluggable storage engines• 2008 Jan – MySQL AB acquired by Sun for $1bn• 2008 Nov – MySQL 5.1 GA• 2008 Dec – Monty Program founded • 2008 Dec – XtraDB released• 2009 Apr – Oracle acquire Sun for $7.4bn• 2010 Feb – MariaDB 5.1 alpha released• 2010 Dec – MySQL 5.5 GA released• 2011 Sep – Oracle: closed source modules for

MySQL


MySQL AB 3.23 4.0 4.1 5.0 5.1 5.2 6.0

Sun 5.1 5.2 5.4 6.0

Oracle 5.4 5.5 5.6 6.0

MySQL Versions through time

What about MariaDB ?


MariaDB

First released in December 2010

community friendly

100% opensource

Oracle closed source feature implemented as opensource

– Thread pool

– external authentification (LDAP)

–


MariaDB development model

Fully transparent Roadmap

Monty Program : – ~30 core MySQL developers around the world

Community Commiters :– Facebook : compression

– Twitter : david Arnaut

– Taobao : multimaster replication

– Galera people

The place where innovation arounfd MySQL will happen : new contributions to come


MariaDB 5.1 – Feb 2010

MariaDB 5.1 = MySQL 5.1 + the following :

Storage Engines– PBXT*

– XtraDB

– FederatedX

– Aria

Bugfixes

Removal of Mutexes


MariaDB 5.1

Microsecond support– Slow query log, SHOW PROCESSLIST etc

Thread pool*– Pool of threads instead of one thread /connection

MariaDB [(none)]> select id, time, time_ms, command, state -> from information_schema.processlist, (select sleep(2)) t;+----+------+----------+---------+-----------+| id | time | time_ms | command | state | +----+------+----------+---------+-----------+ | 37 | 2 | 2000.493 | Query | executing | +----+------+----------+---------+-----------+1 row in set (2.00 sec)


Table Elimination

create view actors as select ACNAM_Name, ACDOB_birthdate, ACRAT_rating from ac_anchor left join ac_name on ac_anchor.AC_ID=ac_name.AC_ID left join ac_birthdate on ac_anchor.AC_ID=ac_birthdate.AC_ID left join ac_rating on (ac_anchor.AC_ID=ac_rating.AC_ID and

ac_rating.ACRAT_fromdate = (select max(sub.ACRAT_fromdate)

from ac_rating sub where sub.AC_ID = ac_rating.AC_ID))

select ACRAT_rating from actors where ACNAM_name='Gary Oldman'

Actor

Name

Birth date

Rating

1 n


MariaDB 5.2 – Nov 2010

MariaDB 5.2 = MariaDB 5.1 + the following:

Pluggable authentication– Authentication handled by plugins

– PAM plugin included

User statistics– CLIENT_STATISTICS

– USER_STATISTICS

– INDEX_STATISTICS

– TABLE_STATISTICS


MariaDB 5.2

Virtual Columns– PERSISTENT or VIRTUAL

Sphinx Storage Engine– Allows access to Sphinx through MySQL

Segmented MyISAM key cache– Key cache divided into different segments

– Allows for better key cache concurrency

– Between 1 and 64 segments


Segmented Key Cache


MariaDB 5.3 – Jan 2012


Handler socket– Direct access to InnoDB/XtraDB storage layer

– No SQL statements

– Simple CRUD operations on tables

– Can be much faster for large batch operations

Dynamic columns– Allows you to create columns with dynamic content

– Basically a blob with handling functions


Dynamic Columns

MariaDB [test]> create table t1 (id int auto_increment primary key, -> name varchar(40), -> type enum ("shirt", "phone", "computer"), -> price decimal(10,2), -> dynstr mediumblob);Query OK, 0 rows affected (0.11 sec)

MariaDB [test]> insert into t1 (name, type, price, dynstr) values -> ("Funny shirt", "shirt", 10.0, COLUMN_CREATE(1, "blue", 10, "XL")), -> ("nokia", "phone", 649, COLUMN_CREATE(1, "black", 2, "touchscreen")), -> ("htc Desire hd", "phone", 579, COLUMN_CREATE(1, "black", 3, "Android")), -> ("BM/Lenovo Thinkpad X60s", "computer", 419, COLUMN_CREATE(1, "black", 3, "Linux"));Query OK, 4 rows affected (0.04 sec)Records: 4 Duplicates: 0 Warnings: 0

MariaDB [test]> select id, name, type, price, length(dynstr) as len, column_list(dynstr) as list from t1;+----+-------------------------+----------+--------+------+------+| id | name | type | price | len | list |+----+-------------------------+----------+--------+------+------+| 1 | Funny shirt | shirt | 10.00 | 17 | 1,10 || 2 | nokia | phone | 649.00 | 27 | 1,2 || 3 | htc Desire hd | phone | 579.00 | 23 | 1,3 || 4 | BM/Lenovo Thinkpad X60s | computer | 419.00 | 21 | 1,3 |+----+-------------------------+----------+--------+------+------+4 rows in set (0.03 sec)


MariaDB 5.3


Replication enhancements– Original statement logged with RBR events

– Checksum for binlog events

– RBR fixed for tables with no PK

– Consistent snapshot between storage engines

User feedback plugin

Extended OpenGIS


Progress Report

MariaDB [employees]> alter table salaries engine = maria;Stage: 1 of 2 'copy to tmp table' 17.55% of stage done

MariaDB [employees]> select id, user, db, command, state,-> time_ms, progress from information_schema.processlist;+---------+-------------------+-----------+----------+| command | state | time_ms | progress |+---------+-------------------+-----------+----------+| Query | copy to tmp table | 23407.131 | 17.551 |+---------+-------------------+-----------+----------+1 row in set (0.47 sec)

Progress report for ALTER TABLE


Optimizer Enhancements

Sub-query optimizations

Join additions

Optimizations for derived tables and views

Disk access optimization

Optimizer control


Group Commit

XtraDB / InnoDB


MariaDB 5.5 / April 2012

MySQL 5.5 + MariaDB 5.3 features + the following:

New optimized thread pool implementation– Pool size dynamic

– Different implementation on Linux and Windows

– Fine grained tuning possible on Linux

@@skip_replication

LIMIT ROWS EXAMINED

MariaDB [employees]> SELECT * from t1, t2 -> LIMIT 10 ROWS EXAMINED 1000;


Optimizations comparison

Feature MariaDB 5.3/5.5

MySQL 5.5

MySQL 5.6

Index Condition Pushdown (ICP) Yes Yes

Disk-sweep Multi-range read (DS-MRR) Yes Yes

DS-MRR with Key-ordered retrieval Yes

Index_merge / Sort_intersection Yes

Cost-based choice of range vs. index_merge Yes

ORDER BY ... LIMIT <small_limit> (In 10.0) Yes

Use extended (hidden) primary keys for innodb/xtradb 5.5

Batched key access (BKA) Yes Yes

Block hash join Yes

User-set memory limits on join buffers Yes

Apply early outer table ON conditions Yes

Null-rejecting conditions tested early for NULLs Yes


Optimizations comparisonFeature MariaDB

5.3/5.5MySQL 5.5 MySQL 5.6

Subquery: In-to-exists Yes Yes Yes

Subquery: Semi-join Yes Yes

Subquery: Materialization Yes Yes

Subquery: NULL-aware Materialization Yes

Subquery: Cost choice of materialization vs. in-to-exists

Yes

Subquery: Cache Yes

Subquery: Fast explain with subqueries Yes

Delayed materialization of derived tables / materialized views

Yes Yes

Instant EXPLAIN for derived tables Yes Yes

Derived Table with Keys optimization Yes Yes

Fields of merge-able views and derived tables used in equality optimizations

Yes


Optimizations comparison

Feature MariaDB 5.3/5.5

MySQL 5.5 MySQL 5.6

LIMIT ROWS EXAMINED rows_limit 5.5

Systematic control of all optimizer strategies Yes Partial

Explain for DELETE, INSERT, REPLACE, and UPDATE

Yes

EXPLAIN in JSON format Yes

More detailed and consistent EXPLAIN for subqueries

Yes


Why MariaDB 10.0

MariaDB 5.5 already have most (+ a lot more) of the optimizer features of MySQL 5.6

MariaDB 5.5 is already a superset of MySQL 5.5. MySQL 5.6 will only have a fraction of the MariaDB 5.5 new features.

A full merge of MySQL 5.6 into MariaDB 5.6 is a one year project as a lot of the code has to be completely rewritten.

→ Better to do the merge in 3 steps into 10.0, 10.1 and 10.2


MariaDB 10.0 trees

Work on 10.0 is already started and first alpha released. One can follow or participate on it by looking at the trees in launchpad:

– 10.0-base tree holds new and rewritten features

– 10.0 tree contains merge of 10.0-base and some MySQL 5.6 features (InnoDB, performance schema)

MariaDB 10.0.0 was released in November and we aim to have a gamma in December/January.

10.0, 10.1 and 10.2 are planned to be released as GA with ½ years interval's.


What are planned for MariaDB 10.0 ?Things already back ported from MySQL 5.6:

– All InnoDB changes (done)

– Performance schema changes (done)

– Read only transaction (significant InnoDB optimization) (done)

5.6 features that are reimplemented:

– Better error message (with system error string) (done)

– NOW() as default value for datetime (in progress)

– Global transaction ID for replication (in progress)

New features:

SHOW EXPLAIN (see what other thread is doing) (done)

Multi source replication

Faster ALTER TABLE with UNIQUE index (in progress)

Even faster group commit (in progress)

Store engine for Cassandra (done)


What are planned for MariaDB 10.x ?

This list of proposed features is still work in progress, and depends on the community and customers.

GIS

– OpenGIS compliance (largely done). MariaDB can already work with OpenGIS data!

– Deeper integration of GIS with optimizer

More online operations

– Analyze table

– ALTER ONLINE TABLE

Compatibility & usability

– IPv6 type

– Query logging and summary per query

– Audit for specific users


What is planned for MariaDB 10.x ?

Replication– Extend group commit to have one sync per group commit

– Parallel applying of binary log in slave

– ALTER TABLE's will be applied in parallel

Statistics and monitoring– Better EXPLAIN

– Persistent table statistics

– Log all SQL errors

– Progress indicator for SELECT


What is planned for MariaDB 10.x ?

Optimizer

– Implement UNION ALL without usage of a temporary table

– Grace HASH join and Sort merge join (Need sponsors)

Performance

– Better multi CPU performance above 16 cores

– More scalable query cache under higher concurrency

– Faster VIEW (don't open & parse view for every query)

Easy of use

– VARCHAR and BLOB support for memory tables

– Table functions

For full list, see kb.askmonty.org/v/plans-for-56


New LGPL client libraries

LGPL client libraries for C and Java

– C is based on the LGPL library from MySQL 3.23

– API compatible with latest MySQL client libraries.

– Java is based on the drizzle driver.

Works with MariaDB, Percona server, MySQL and drizzle

Developed by Monty Program Ab and SkySQL.

Announced and released 2012-10-29

You can download these from http://mariadb.org

Documentation is still in progress...


MySQL connectors

.NET / JDBC / C

Python

PHP native driver (bsd licence)

Oracle Connector are GPL not LGPL

LGPL connectors are available : – This is important for OEM as this means no

commercial licence is required.• C and Java connectors availables

Good pres by Andrew Hutchings on various aspects of connectors at PLUK2012


MariaDB and TokuDB

MariaDB and Tokutek have agreed to make TokuDB a native plugin in MariaDB 5.5 and MariaDB 10.0 by end of Q1 2013.

official MariaDB binary will be able to dynamically load the TokuDB storage engine directly (no patches needed for MariaDB).

TokuDB will be added to the MariaDB buildbot test suite

TokuDB will be available for download from https://downloads.mariadb.org/ together with MariaDB.

About TokuDB

- TokuDB uses Fractal Tree® indexing to improve insert and query speed, compression, replication performance, and online schema flexibility.


Connect storage engine

MariaDB 10.0 will include the Connect storage engine by Olivier Betrand.

With the connect storage engine you can read, write and update files in a lot of different storage formats:

Various fixed and dynamic text formats

.DBF (dBASE format) / .CSV / .INI / .XML

ODBC ; Table extracted from an application accessable with ODBC

http://mariadb.org/


MariaDB Foundation Overview

– The Foundation is the new driver of the MariaDB project

– Custodian of the code, Guardian of the community

– Foundation can never to be controlled by a single entity or person

– Foundation designed to be self-sustaining


MariaDB Foundation Details

A US 501c(3) not-for-profit

8 founders and 2 sponsors so far (including all MySQL founders!)

Open for more founders until February

In February the founders will the choose board etc.

In the interim we have:

– Monty as CTO

– Andrew Katz as COO and Legal Person (checking all the paperwork)

– Niall McCarthy as Business Development (signing up founders)


MariaDB Foundation Goals

That MariaDB be actively developed in the community and to:

– Increase adoption of MariaDB

– Ensure sustainable high-quality efforts to build, test and distribute MariaDB

– Ensure that community patches are reviewed and adopted

– Guarantee a community voice

– Keep MariaDB compatible with MySQL

– Maintain mariadb.org


MariaDB Foundation

More founders and sponsors are welcome!

If you care about the future of the MySQL ecosystem, please contact us and ask how you can get involved!

Niall McCarthy [email protected]

Michael Widenius [email protected]

Andrew Katz [email protected]


Questions / ideas / disagreements ?

For questions later, use the public MariaDB email list at

[email protected] or IRC #maria on Freenode.


MariaDB-galera

MariaDB working closely with Codership to release MariaDB 5.5 with Galera (a multi-master solution).

MariaDB 5.5 galera was released as Alpha in September.


Getting MariaDB

http://mariadb.org is the main place

Available via OpenSUSE build services

Also available via – Gentoo

– FreeBSD

– Homebrew

– Slackware

– ArchLinux

yum and apt repos available from MP

mailto:[email protected]




More Information

Downloads: mariadb.org/

Mailing lists on launchpad

#maria on freenode

Knowledgbase: kb.askmonty.org/

Support:www.skysql.com/products/skysql-enterprise

Training & consulting: www.skysql.com/services/mysql/overview



MySQL use cases : much wider than before

Bigger volumes : partitionning

Number of transactions : multi bufferpool ...

Complexité des requêtes : improved optimizer

Availability : crash safe replication / semisync

Securité : auth plugin, password policy ...

Operation : on line backup, performance schema

Should we say "Enterprise class database" ?


MySQL multi cores BenchmarkFast on various workload with many cores :

– 48 is ok 64 better in some cases

Here InnoDB FTS bench

From Dimitri Kavtchuk blog : http://dimitrik.free.fr/blog/index.html

http://mariadb.org/


MySQL multi cores Benchmark

Sysbench Read only on 4/8/16/24/32 cores




Sysbench Read only range

on 4/8/16/24/32 cores




Sysbench RW on 32 cores



NoSQL with MariaDB

MariaDB 5.5 handlersocket

Nodejs connector pour MariaDB utilisant async

Leveldb storage engine

Cassandra storage engine

NoSQL de Mysql 5.6 Memcached

Advantage : noSQL + transactions and consistency. SQL available


Percona Server

First released in Dec 2008

XtraDB was ahead of innoDB– Kinoshita developer now at Oracle

– Google & Facebook patches originally

– More instrumentation

– Faster restart

Microsecond support / Better statistics

Most improvements now part of the standard innoDB


MariaDB vs Oracle MySQL

Oracle tries to Catch up on MariaDB(optimizer ...)

More and more closed source extension

Oracle closing bug db (for security reason)

Closed MySQL forge / university /wiki : a lot of valuable materials lost

No sharing of code during dev / closed design

Not releasing all test cases.

License commerciale (limited right to use / time)

More and more closed source Extensions

Lock-in strategy


Oracle and open source

Lots of stories: – openoffice, open solaris, open sso, open ds, hudson,

glassfish

Btrfs was nice when they did not own ZFS– Creator Chris Mason gone to Fusion IO

Do not share the values of open source– People that believe in open source do not stay

Oracle Linux : Why not share the good stuff if you really want to improve the product (ksplice ..)

73SkySQL Ab 2012 Confidential

MySQL 5.6 What is new ?.


MySQL 5.6 ?

MySQL 5.6 builds on MySQL 5.5 codebase with:

InnoDB for better transactional throughput, availability

Optimizer for better query execution times, diagnostics

Replication for higher availability, data integrity

Performance Schema for better instrumentation

Various others improvements


MySQL 5.6 innoDB improvements

Online DDL Operations

Optimized for Read Only workloads

SSD Optimizations4, 8k page sizes.ibd files outside of MySQL data dirseparate tablespaces for undo log

Dump and restore/warm buffer pool

Persistent Optimizer Statistics

FULLTEXT indexes on InnoDB tables

Transportable Tablespaces


MySQL 5.6: Replication

Global Transaction Ids

MySQL 5.6: Replication HA Utilities (Python)

Multi-Threaded Slaves

Binary Log Group Commit

MySQL 5.6: Crash safe Slaves

MySQL 5.6: Replication Event Checksums


MySQL 5.6: Security

Password handling :

Provide alternatives to showing passwords in plain text

Assess / Enforce password strength policies

Enforce new password at next login

Stronger password hashing


Others

Improved Partitioning– up to 8k partitions per table

– Import/export tables to/from partitioned tables

– Explicit partition selection

MySQL 5.6 Performance Schema

Better defaults values for 5.6

Memcached API


Others things worth considering as they are GPL

MySQL workbench migration from SQLServer / PostgreSQL to MySQL

MySQL Utilities : set of usefull python scripts


Enterprise Monitoring / Auditing Tools

• Oracle’s MySQL Enterprise Monitor (MEM)

• SkySQL Enterprise Monitor (MONYog)• Nagios / Cacti + plugins• Zabbix plugins• mycheckpoint (openark)• MySQL plugins for

– Munin– SNMP– OpenNMS


Backup Tools

MySQL Enterprise Backup

(InnoDB Hot Backup)

mysqldump (of course)

mysqlhotcopy (MyISAM)

XtraBackup

Mylvmbackup

Xtrabakup manager (php)


Modelling and Query Tools

• MySQL Workbench (GPL)• SkySQL Visual Editor (SQLYog)• HeidiSQL• phpMyAdmin• Plenty of closed source tools• Toad for MySQL


Storage EnginesSkySQL can help to chose• Analytics

– Infobright– InfiniDB

• Transactional– TokuDB

• HA/Scaling– ScaleDB– Schooner– Galera

• Others– OpenGraph– FederatedX– Blackhole– Aria

Pbxt / SolidDB / Falcon / Nitro / XtraDB


Conclusion

SkySQL can support you on MySQL/MariaDB

SkySQL can help you to make choices in the ecosystem offers.

MariaDB is the long term future of MySQL

MariaDB Foundation is going to unite everyone and to create a true momentum

SkySQL Cloud MySQL MariaDB

Internet

confidentialskysql ab

mysql developers

confidential mysql

oracle10skysql ab

secondsskysql ab

lot of mysql customers

original founders of

mysql abevp product