my sql vivo_5.5_product_update_pt

<Insert Picture Here>

MySQL Product Update

© 2010 Oracle Corporation – Proprietary and Confidential

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.


MySQL Architecture


Storage Engine - MyISAM

Highlights Default MySQL engine (v5.1 and earlier)

No practical limits on data storage

Very efficient storage

Easily handles high-speed data loads

Has B-tree, R-tree, and Full-text Indexes

Supported by special index memory caches

Offers compressed data option

Supports geospatial operations

Uses table level locks

Does not do transactions

Backup/point-in-time recovery supported

Best Use Cases Data warehouse

High-traffic web sitesMyISAM


Storage Engine - InnoDB

Highlights Provides ACID transaction support

64TB data storage limit per tablespace

Higher storage cost

Slower data load speed than most other engines

Offers MVCC/Snapshot read

Has B-tree and clustered indexes

Supported by special data & index memory caches

Provides foreign key support

Does not offer compressed data option

Uses row level locks and has custom isolation levels

Has crash recovery

Backup/point-in-time recovery supported

Best Use Cases OLTP

InnoDB


Product Announcements


Improved Performance and Scalability• InnoDB becomes default storage engine• Better metadata locking within transactions• Improved performance and scalability on Windows• InnoDB Improvements

Improved Availability• Semi-synchronous Replication• Replication Heartbeat

Improved Usability• SIGNAL/RESIGNAL• More Partitioning Options• PERFORMANCE_SCHEMA

MySQL 5.5GA


MySQL 5 EvolutionReliability

• SQL Mode• Triggers & Views• Precision Math• Increased object support• Enteprise Monitoring Tool

• Row-Based Replication• Disk-based Cluster• Cluster Replication with Conflict Resolution• Enterprise Query Analyser

• Default InnoDB (Barracuda)• Semi-Sync Replication• Enterprise Connectors• Enterprise Support Diagnostics• MySQL Cluster on Windows• Fast InnoDB Recovery

Ease of Use

• Instance Manager• Information Schema• Cursors• Enterprise Backup & Recovery Manager

• XML/XPath Support• Task Scheduler• Storage Engine Plug-in API• CSV Storage Engine

•SIGNAL/RESIGNAL• NDB_INFO Schema• MySQL Cluster Manager• MySQL Workbench 5.2• MySQL Cluster Connectors• MySQL Enterprise Backup

Performance

• Stored Procedures• Cluster query push down• Query optimisations• Archive Engine• InnoDB storage improvements

•Table/Index Partitioning• Full-Text Index Improvements• Faster ALTER TABLE• Faster ADD/DROP Index• Parallel Data Import

• Multiple Buffer Pool and Rollback Segment• Eliminated Lock bottlenecks• Extended Change Buffering & Purge Scheduling• PERFORMANCE_SCHEMA• Multithreaded Cluster

55..0055..00

55..1155..11

55..5555..55ββ


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

Scalability Improvements• Improved Log Sys Mutex• Separate Flush List Mutex• Improved purge scheduling

Better Instrumentation and Diagnostics• InnoDB stats in PERFORMANCE_SCHEMA

InnoDB 1.1 (included in MySQL 5.5)GA


Multiple Buffer Pool

• 5.1: 1 Buffer Pool• 5.5: up to 64 Buffer Pools

The Car Park Analogy•In 5.1, the Car Park had 1 entrance and 1 exit•In 5.5, the Car Park has 64 entrances and 64 exits•The number of spaces available is the same, but cars can get in and out quicker


Multiple Rollback Segments• 5.1: 1 Rollback Segment can handle up to 1023 concurrent “write” transactions

• 5.5: 128 Rollback Segments can handle up to 128k concurrent “write” transactions

The Highway Analogy•In 5.1, the highway had1 lane•In 5.5, the highway has 128 lanes•Each lane can still handle up to 1023 cars per hour and cars run at the same speed, but 128 lanes can handle 128k cars per hour in total


MySQL 5.5 SysBench Benchmarks

MySQL 5.1.40(InnoDB built-in)

MySQL 5.1.40 (InnoDB Plug-in)

MySQL 5.5.4 (New InnoDB)

Intel Xeon X7460 x86_64

4 CPU x 6 Cores/CPU

2.66 GHz, 32GB RAM

Fedora 10

364% performance gain

for MySQL 5.5 over 5.1.40; at scale


%9 9 9 99

35 days 4 days 50 mins 5 mins8 hours

Unmanaged

Replication Technologies

Clustering Technologies

Clustering & GeographicalRedundancy

Well-Managed

SmallBusiness

ISPs &Mainstream

BusinessData

CentersBankingMedical

TelcoMilitaryDefense

.

MySQLCluster

MySQL +Shared-Disk

MySQLReplication

DRBD

MySQL HA Solutions


MySQL Replication

MySQLMySQL

SE2SE1

Storage Engines

Master

Binlog

ReplicationSlave

SQLI/O

Confirm

Application Application

SE2SE1

Storage Engines

Relay


MySQL Cluster

NDBStorage EngineMemory

&Disk

X

X

What Facebook is saying

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 – June 21, 2010

http://www.facebook.com/note.php?note_id=403975340932

http://www.facebook.com/note_redirect.php?note_id=403975340932&h=bc428019e702629ffc6ca1dedb44aeaa&url=http://www.facebook.com/note.php?note_id=217851170932

http://www.mysql.com/support/supportedplatforms/enterprise.html

What Facebook is saying

http://www.facebook.com/note.php?note_id=403975340932

http://www.mysql.com/support/supportedplatforms/enterprise.html


Replication with MySQL 5.5

• 5.1: Asynchronous Replication• 5.5: Asynchronous Replication+ Semi-Synchronous Replication+ Replication Heartbeat

• In 5.1, in case of Master fault, you may lose some data

• In 5.5, in case of Master fault, your data is already saved on a Slave server

• This is the same HA approach adopted by other vendors.


Replication:Asynchronous vs Semi-Synchronous

Asynchronous•Ideal for scalability•In case of Master fault, you may lose some data•Replication has no impact on write operations

Semi-Synchronous•Ideal for availability•In case of Master fault, you will not lose data •Replication has an impact on write operations


MySQL Cluster 7.1 – Key Enhancements

•Simplified Management & Monitoring:•ndbinfo real-time monitoring•MySQL Cluster Manager•Faster system restarts

Reducing Cost of Operations

•MySQL Cluster Connector for Java:•Native Java API•OpenJPA Plug-In

Delivering up to 10x higher Java Throughput

•GA Version - Ready for production

Windows Support

GA


MySQL Cluster Manager and NDB_INFO

• 7.0: DBAs had to rely on scripts and different tools administer and monitor Cluster

• 7.1: Administration is simplified and free from human errors; monitoring is easier

mysql> use ndbinfomysql> show tables;+-------------------+| Tables_in_ndbinfo |+-------------------+| blocks || config_params || counters || logbuffers || logspaces || memoryusage || nodes || resources || transporters |+-------------------+

mysql> use ndbinfomysql> show tables;+-------------------+| Tables_in_ndbinfo |+-------------------+| blocks || config_params || counters || logbuffers || logspaces || memoryusage || nodes || resources || transporters |+-------------------+


Java Access Performance


MySQL Enterprise Monitor 2.3

• Performance Optimization for Java and .NET applications

• Improved Performance Monitoring• MySQL Enterprise Connector Plugins to Query

Analyzer• MySQL Query Analyzer Advanced Search Options• New Query Analyzer Execution Notices

• Filter for Specific Query Problems • Full Table Scans, Bad Indexes

• Improved User/Security Model• New Read Only User• New LDAP Authentication

• Improved Integration with MySQL Support• New MySQL Support Diagnostic Reports

GA


MySQL Enterprise Backup

• Formerly “InnoDB Hot Backup”• Online, non-locking backup & recovery

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

• Logical and physical backups• Full or incremental backups• Supports InnoDB and MyISAM• Cross-Platform (Windows, Linux, Unix)• Features

• Point-in-time recovery• Compressed backups• Partial Backup

Beta


MySQL Workbench 5.2

• Three Tools in One Product• SQL Editor• Database Administrator• Data Modeler

• Cross Platform and Native UI• Windows• Linux• Mac OS X

GA


Cut Costs in Improve Efficiencies– Eliminate downtime & related business and IT costs

– More options for HA and Replication

– Easily scale vertically and/or horizontally as demand grows

Better Tools for Managing Change– MySQL Workbench – All-In-One Administration, Modeling, SQL Editor

– MySQL Enterprise Monitor – proactive problem resolution

– API and Application Language Enhancements

Better integration– With Oracle products

– LAMP

– Windows

Benefits of MySQL 5.5Cut Costs, Better Tools, and Better Integration


The preceding 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.

my sql vivo_5.5_product_update_pt

Documents

confidential mysql

oracle corporation proprietary

better mysql

mysql architecture

mysql mysql focus areas

sole discretion of oracle

glassfish mysql php

mysql product update