<Insert Picture Here>

Pavan VenkateshSenior Sales Consultant

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

AGENDA

Oracle's Investment in MySQL

New Packaging and Pricing

MySQL Enterprise tools

MySQL current and future releases

Q&A

Complete. Open. Integrated. Two more important attributes

• Oracle never settles for being second best at any level of the stack

• “Complete” means we meet most customer requirements at every level

That’s why MySQL matters to Oracle and Oracle

customers

Oracle’s Investment in Open Source

• Supported popular open source projects for many years• Part of Oracle’s Complete, Open, Integrated strategy• Speed up time-to-innovation• Expand the developer community

Investment in MySQLRapid Innovation

• Make 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

Oracle + MySQL Customers

•Product Integration– Oracle GoldenGate – Oracle Enterprise Linux + Oracle VM – Oracle Secure Backup – Oracle Audit Vault – Oracle Enterprise Manager

•Support– Leverage 24x7, World-Class Oracle Support– MyOracle Support

Filesystems, Files and LogsRedo, Undo, Data, Index, Binary, Error, Query and Slow

Pluggable Storage Engines ArchitectureConnectors

Native C API, JDBC, ODBC, .Net, PHP, Ruby, Python, VB, Perl

Connection PoolAuthentication – Thread Reuse – Connection Limits – Check Memory – Caches

Enterprise Management

Services and Utilities

Backup & Recovery

Security

Replication

Cluster

Partitioning

Instance Manager

Information_Schema

MySQL Workbench

SQL InterfaceDDL, DML, Stored

Procedures, Views, Triggers, Etc..

ParserQuery Translation, Object Privileges

OptimizerAccess Paths,

Statistics

CachesGlobal and Engine

Specific Caches and Buffers

Pluggable Storage EnginesMemory, Index and Storage Management

InnoDB MyISAM Cluster Etc… Partners Community More..

MySQL Server

Clients and Apps

Storage Engines

Dynamically add and remove storage engines.Change the storage engine on a table with “ALTER TABLE …”

HighHighLowHighLowMemory cost (relative to other engines)HighMedHighestHighHighBulk insert speedYesYesYesYesYesReplication support

NoNoNoYesNoBuilt-in Cluster/High-availability support

NoYesNoNoNoForeign Key support

NAMedSmallMedSmallStorage cost (relative to other engines)

NoYesYesNoYesCompressed dataNAYesNoYesYesIndex cachesNAYesNoYesNoData cachesNoYesYesNoYesGeospatial support

NoYesNoNoNoMVCC snapshot readTableRowRowRowTableLocking granularity

NoYesNo YesNoTransactions

Yes64TBNoNoStorage limits

MemoryInnoDBArchiveNDBMyISAMFeature Yes

Great News for Customers

We have simpler packaging now One Unified support for all the products MySQL Cluster support price is catchy now More value add-ons with the same price

New Packaging and Pricing

New MySQL support

MySQL High Availability Solutions

MySQL Replication MySQL Replication and Heartbeat MySQL Cluster MySQL Cluster Carrier Grade Edition Other HA solutions

Current MySQL Releases

MySQL 5.1

• Partitioning• Row-based and Hybrid Replication• Task Scheduler • Embedded Library • Better Performance Utilities

InnoDB Plug-in 1.0.7 (GA)

• Shipped with MySQL 5.1.46• Improved Performance, Scale & Throughput• Fast ADD/DROP Index• New File Format Management• Data compression for much smaller tables• Improved Manageability & Efficiency

Improved Performance, Scale – Yes!

Improved Administration• NDBINFO: Real time status & usage statistics• MySQL Cluster Manager (CGE Only)

Higher Performance• MySQL Cluster Connector for Java • Native Java & OpenJPA access to MySQL Cluster

Carrier Grade Availability & Performance • Shared nothing, distributed design for 99.999% availability• Sub-Second Failover & Self Healing Recovery• On-Line Scaling and Maintenance• Parallel Multi-Master Architecture• Low Latency, Real Time Responsiveness

MySQL Cluster 7.1GA

• Single, consolidated view into entire MySQL environment

• Auto-discovery of MySQL servers, replication topologies

• Customisable rules-based monitoring and alerts

• Identifies problems before they occur

• Reduces risk of downtime

• Makes it easier to scale out without requiring more DBAs

MySQL Enterprise Monitor

MySQL Enterprise Monitor 2.3

• New MySQL and OS graphs– Disk I/O and space– Network throughput

• New Cluster advisors and graphs– Memory– Node up/down status

• InnoDB 1.1 graphs• Faster Problem Resolution

– MySQL Support diagnostic reports

GA

MySQL and MyOracle Support

MySQL Enterprise Monitor • Collect MySQL diagnostics and upload to MOS SR (now!)• Track SRs from Enterprise Dashboard • Create/maintain SRs (in future)• Saves DBA time

• collecting data for Support team, tracking status

MySQL Enterprise Backup

Formerly “InnoDB Hot Backup” InnoDB Hot Backup is rebranded as MySQL Enterprise

Backup• Online, non-locking backup & recovery

– Tables, Indexes– Server, database, or object-level

• Point-in-time recovery• Compressed backups• Also provides backup & recovery for MyISAM• Cross-Platform (Windows, Linux, Unix)

MySQL Workbench 5.2• SQL Development

– SQL Editor - Color Syntax Highlighting – Connection Management - Wizard, SSH Tunnel– Multi-Pane Results View, In-grid data edits

• Database Administration– Status, Configuration, Start/Stop, Replication– Users, Security, Session Management– Import/Export Dump Files

• Data Modelling– Visual Design – Forward/Reverse Engineer

GA

MySQL Future Products

MySQL 5.5

• InnoDB 1.1 would become the default storage engine• Higher performance & Scalability• Scales up to 32 cores• Semi-synchronous replication

• Improves the reliability of failover• COMMITs on the Master node are acknowledged only when at least one of the Slave

nodes has logged the event• Data is not lost in case of failover

• Replication heartbeat• Avoids spurious relay log rotation when the Master node is idle• Replication delay is more accurate

RC

MySQL 5.5 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

mysql> SELECT EVENT_ID, EVENT_NAME, TIMER_WAIT

-> FROM EVENTS_WAITS_HISTORY WHERE THREAD_ID = 13

-> ORDER 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 |+----------+-----------------------------------------+------------+

New Features in InnoDB 1.1

• Multiple Buffer Pool Instances– Prior to InnoDB 1.1: All threads had to acquire exclusive access to a

single buffer pool– Minimise contention by assigning DB pages randomly to one of the

buffer pools

• Multiple Rollback Segments– Prior to InnoDB 1.1: A Rollback Segment can handle up to 1023

concurrent “write” transactions– InnoDB 1.1: the Rollback segment is divided into 128 segments. Each

segment supports 1024 concurrent W transactions, i.e. 128k concurrent W transactions

– Significant improvement with 32+ cores

• Extended InnoDB change Buffering• Native Asynchronous I/O on Linux• Improved Purge Scheduling

RC

Improved Recovery Performance – BenchMark

• Crash recovery with dbt2 test• 50 warehouses• database (9800MB )• innodb_log_file_size = 2x1950MB • buffer_pool=12GB • started test and kill after 5 mins.

Total (min)

Scanning Log Applying

Plugin 1.0.6 192 75 117

InnoDB 1,1 20 17.7 2.3

Improvements

9.6 4 51

Crash Recovery

0

50

100

150

200

250

Total Scanning Log Applying

Min

utes

plugin 1.0.6InnoDB 1.1

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 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

RC

MySQL 5.5 SysBench BenchmarksLinux

MySQL 5.1.50(InnoDB built-in)

MySQL 5.1.50 (InnoDB Plug-in)

MySQL 5.5.6 (New InnoDB)

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

Fedora 10

369% performance gain

for MySQL 5.5 over 5.1.50; at scale

RC

MySQL 5.5 SysBench BenchmarksWindows

MySQL 5.1.50(InnoDB built-in)

MySQL 5.1.50 (InnoDB Plug-in)

MySQL 5.5.6 (New InnoDB)

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

538% performance gain

for MySQL 5.5 over 5.1.50; at scale

RC

MySQL 5.5 SysBench BenchmarksWindows

MySQL 5.1.50(InnoDB built-in)

MySQL 5.1.50 (InnoDB Plug-in)

MySQL 5.5.6 (New InnoDB)

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

1561% performance gain

for MySQL 5.5 over 5.1.50; at scale

RC

OLTP RW less read

MySQL 5.5 Early Adopters Speak!•

Thanks to the MySQL and InnoDB teams for their continued hard work and dedication to making MySQL faster as hardware evolves. I, for one, cannot wait to see what this stuff does for us. “

– Jeremy Zawodny, Craigslist

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

•My expectations for 5.5 were not high. I am pleasantly surprised!”

– Mark Callaghan, Facebook, MySQL UC Keynote

I previously tested InnoDB on an 8-core server to determine how many IOPs it can do for a simple IO-bound workload. The limits were ~12k disk reads/second for MySQL 5.0 and ~18k reads/second for MySQL 5.1. I just repeated the tests using a 16-core server and the results are much better. I can get 20,000 to 30,000 disk reads/second using InnoDB 5.1. InnoDB 5.5 appears to be capable of 50,000 to 70,000 disk reads/second courtesy of support for multiple buffer pools (innodb_buffer_pool_instances).

•Mark Callaghan’s Blog, Facebook - 21 June 2010

What Facebook is telling about 5.5

MySQL Proxy

• Load balancing

• Fail over

• Query Analysis

• Query Filtering

MySQL Product ReleasesContinuous Innovation

MySQL 5.5Beta

Q1 CY2010 Q2 CY2010 Q3 CY2010 Q4 CY2010

MySQL Enterprise Monitor 2.2GA

MySQL Workbench 5.2GA

MySQL 5.5MySQL Enterprise Monitor 2.3

General Availability

MySQL Cluster 7.1GA

A Better MySQL

MySQL 5.5RC

Key Takeaways

• MySQL is important to Oracle and our customers– Part of our Complete, Open, Integrated strategy

• Oracle is making MySQL better today– Major Feature, Performance, Scalability enhancements– 24x7, Global support in 145 countries with Unified support– More add-ons for the same price

Safe home for MySQL

Q&A