Seminar : "The Future of MYSQL - Roadmap to Success" session MySQL Technology Update

<Insert Picture Here>

MySQL Technology UpdateOracle’s Investment in Performance and Scalability

Investment in MySQLRapid InnovationMake MySQL a Better MySQL• #1 Open Source Database for Web Applications• Most Complete LAMP Stack• Telecom & Embedded

Develop, Promote and Support MySQL• Improve engineering, consulting and support• Leverage 24x7, World-Class Oracle Support

MySQL Community Edition• Source and binary releases• GPL license

Making MySQL Better Today and Everyday

Announced TodayMySQL 5.5 is now GA!

Better Performance, Scalability and Recovery

InnoDB Performance improvements• Multiple Buffer Pool Instances• Multiple Rollback Segments – now supports 128K concurrent trxs• Extended Change Buffering (with delete buffering, purge buffering)• Improved Purge Scheduling• Improved Log Sys mutex, Separate Flush List mutex• Improved Recovery Times• More…

MySQL Performance Improvements• Better Metadata Locking within Transactions• Split LOCK_open mutex• Eliminated LOCK_alarm mutex as bottleneck• Eliminated LOCK_thread_count as bottleneck• Improved Performance/Scale on Win32, 64• More…

MySQL 5.5 – What’s NewGA

InnoDB becomes default storage engine• ACID Transactions, FKs, Crash Recovery

Improved Availability• Semi-synchronous Replication• Replication Heartbeat• Replication Slave fsync options• Automatic Relay Log RecoveryImproved Usability• SIGNAL/RESIGNAL• More Partitioning Options• Replication Server Filtering• Replication Slave Side Type Conversions• Individual Log FlushingBetter Instrumentation/Diagnostics• New PERFORMANCE_SCHEMA

MySQL 5.5 – What’s NewGA

“Thanks to the MySQL and InnoDB teams for their continuedhard work and dedication to making MySQL faster ashardware evolves. I, for one, cannot wait to see what thisstuff does for us. “– Jeremy Zawodny, Craigslist

“I’m really blown away by MySQL 5.5’s improvements. “- Don MacAskill, SmugMug

“My expectations for 5.5 were not high. I am pleasantlysurprised!”- Mark Callaghan, Facebook, MySQL UC Keynote

MySQL 5.5 Early Adopters Speak!

MySQL 5.5 SysBench BenchmarksLinux

Intel Xeon X7460 x86_64 4 CPU x 6 Cores/CPU 2.66 GHz, 32GB RAM Fedora 10

MySQL 5.1.50(InnoDB built-in)

MySQL 5.1.50 (InnoDB Plug-in)

MySQL 5.5.6 (New InnoDB)

200% performance gainfor MySQL 5.5 over 5.1.50; at scale

GA

MySQL 5.5 SysBench BenchmarksLinux






GA

MySQL on WindowsThe Right Choice

Significant Developer Adoption• Windows is the #1 development platform for MySQL• Making MySQL better on Windows

Performance & Scalability• Improved on Windows• MySQL 5.5 Benchmarks

Lower TCO• More Affordable• Easier to Administer

Ease of Use• MySQL Workbench• New Connector/NET 6.3

Cross-platform• 20+ Platforms• No Lock-in

MySQL 5.5 SysBench BenchmarksWindows




Intel x86_644 CPU x 2 Cores/CPU3.166 GHz, 8GB RAMWindows Server 2008


GA

MySQL 5.5 Scales on multi core SysBench Read Write GA

MySQL 5.1

MySQL 5.5.3

MySQL 5.5.4

AMD Opteron 7160 (Magny-Cours) @2100 MHz 64 GB memory 2 x Intel X25E SSD drives OS is Oracle Enterprise Linux with the Enterprise Kernel 4 sockets with a total of 48 cores.

Tran

sact

ions

/Sec

ond

Crash Recovery

0

50

100

150

200

250

Total Scanning Log Applying

Min

utes

plugin 1.0.6InnoDB 1.1

Improved Recovery PerformanceGA

5.1 5.1 5.1

5.5 5.5 5.5


50 warehousesDatabase=9800MBInnodb_log_file_size=2x1950MBBuffer_pool-12GBStarted tested, killed server@5 mins

> 10x recovery performance gainfor MySQL 5.5 over 5.1

Copyright Oracle Corporation 2010 19

MySQL 5.5 Replication Features

1. Semisynchronous replicationImproved resilience by having master wait for slave to receiveevents.

2. Slave fsync tuning & Automatic relay log recoveryTune fsyncs so corruption is less likely on slave crashes.Let the slave recover from corrupted relay logs.

3. Replication HeartbeatHave a more precise failure detection mechanism.Avoid spurious relay log rotation when the master is idle.

4. Per server replication filteringInstruct slave to discard events from a master with a specificserver id.


MySQL 5.5 Replication Features

5. Precise Slave Type ConversionsUse different types on master and slave and getautomatic type promotion and demotion when usingRBR

6. Individual Log FlushingSelectively flush server logs when using 'FLUSHLOGS'

7. Safe logging of mixed transactionsReplicate transactions containing both InnoDB andMyISAM changes


1. Semisynchronous Replication

• MySQL replication is asynchronous– A recovered master may have non-binlogged changes.– This can cause master and slave to diverge.– A failed master may have binlogged but non-replicated

changes– If a slave is promoted to master some information can be lost.

• Semisynchronous replication ensures redundancy– At least one slave acknowledges relay logging the transaction.– Master waits for slave acknowledgement before commit

returns.– (On time-out, master temporarily switches to async replication.)

On masterRpl_semi_sync_master_statusRpl_semi_sync_master_clientsRpl_semi_sync_master_yes_txRpl_semi_sync_master_no_tx

On SlaveRpl_semi_sync_slave_status

Checking the state



MySQL Server

SE2SE1

Master

Binlog

Replication MySQL Server

SE2SE1

Slave

RelayBinlog Binlog

I/Othread

• Automatic checking of connection status• No more relay log rotates when the master is idle• Detection of master/slave disconnect, configurable in milliseconds

CHANGE MASTER SET master_heartbeat_period= val; SHOW STATUS like 'slave_heartbeat period' SHOW STATUS like 'slave_received_heartbeats'

3. Replication Heartbeat

Heartbeat


MySQL: Still Free, Open to the Community

http://mysql.com/downloads/

Available to download and use under the GPL:• MySQL Database (Community Server)

• All 5.5 features, all storage engines• MySQL Cluster

• Geo-replication• MySQL Workbench Community Edition• MySQL Connectors• MySQL Proxy• Documentation• Forums

Seminar : "The Future of MYSQL - Roadmap to Success" session MySQL Technology Update

Technology

Transcript of Seminar : "The Future of MYSQL - Roadmap to Success" session MySQL Technology Update