Since the acquisition, Oracle has delivered more products, at a higher quality, than at any time in MySQL history.
MySQL 5.6 delivers across the board improvements designed to enable innovative DBAs and Developers to create and deploy the next generation of web, embedded and Cloud/SaaS/DaaS applications on the latest generation of development frameworks and hardware platforms.
At a glance, MySQL 5.6 is simply a better MySQL with improvements that enhance every functional area of the database kernel, including:
Improved Performance Scalability 5.6 scales up 48 CPU threads which enables users to leverage the full processing power of modern architectures 5.6 performs up to 230% faster over 5.5 on transactional work loads. Improved InnoDB Allow 5.6 to provide better transactional throughput and availability over previous versions. Improved Optimizer Provides better query execution times and more diagnostics for monitoring, tuning and debugging Impoved Replication Provides higher performance, availability and data integrity Improved Performance Schema Provides better instrumentation and user/application level statistics and monitoring New! NoSQL Access to InnoDB Provides fast, Key Value access with full ACID compliance, better developer agility
Improved InnoDB storage engine for better transactional throughput Improved Optimizer for better query execution times and diagnostics Better Application Availability with Online DDL/Schema changes Better Developer Agility with NoSQL Access with Memcached API to InnoDB Improved Replication for high performance, self-healing distributed deployments Improved Performance Schema for better instrumentation Improved Security for worry-free application deployments And other Important Enhancements
Ability to get MySQL components not yet packaged by their Linux distro. Access to the latest and greatest versions of MySQL, even if they have not yet been adopted by their Linux distro. Packages of MySQL products supported by Oracle. Easy early access to pre-GA product releases, such as MySQL 5.7 Development Milestone Releases.
And let me give you some figures to illustrate our efforts
The 1667 number is bugfixes on 5.6 only. The 2909 number is bugfixes since time of 5.5 GA, but for all releases 5.0/5.1/5.5/5.6
And as we can see in this example of MySQL 5.6, we’re developing the products releasing ‘early and often’, with predictable DMRs allowing the MySQL Community, i.e. you, to provide us with feedback and input during the development.
And we’re also delivering early access features via labs.mysql.com to allow you to provide feedback very early on in the process.
Good to refer that we are integrating MySQL with all relevant Oracle products to make it easier to use for Oracle customers (Oracle Secure Backup, Oracle Database Firewall, Oracle Enterprise Manager…etc).
MySQL is in an incredibly favorable position, and the platform of choice for next generation Web, mobile and cloud applications.
It is....(the 4 key points)
We’re also seeing great momentum for MySQL: talk about 3 points on the side
We want to ensure that MySQL remains the platform of choice for next gen web apps, and we are evolving the database by developing new features, enhancements and integrating in it new capabilities useful for modern apps. Give example of the 2 other points in orange (NoSQL and new languages)
Oracle/MySQL has the answers you need in MySQL Enterprise Edition.
Real-time MySQL Performance and Availability Monitoring Visual Dashboad for Better Visibility Visually Find and Fix Problem Queries Pinpoint SQL code that causing a slowdown Visual Capacity Planning Forecasting using Projections and Trend Analysis Agentless, Cloud Friendly Architecture Remotely Monitor MySQL without agents Start Monitoring MySQL in 10 minutes Easy to use with zero configuration
Just a quick intro at this point – all of this is covered in more details later in the presentation.
It’s intent is to simplify life by providing automation around High Availability and scaling out through horizontal sharding.
Fabric maintains a set of mappings from shard key to shards; the connectors cache that information and use it to route SQL transactions directly to the correct MySQL Server using a shard key provided by the application – no extra hop is needed and so latency is kept to a minimum. Initially, Fabric-aware connectors are provided for Python, PHP and Java. We are also providing patches for Hibernate and Doctrine.
We recognize that in many cases it is undesirable or impossible for the application or middleware code to be updated to provide a shard key and so the addition of transparent sharding is a development priority.
Within a shard (or Master Group), there are one or more MySQL Servers that are capable of being the replication master and then also a set of replication slaves that can be used to scale out reads *within* the shard. This is based on MySQL 5.6 Global Transaction ID based replication.
Shards can be split and moved; the window of unavailability is kept to a minimum but it is not yet a fully on-line operation.
Global updates are supported and allow, for example, schema changes to propagate to all shards. This feature allow you to have global tables that are common to all shards and can be updated globally.
Can download it from labs.mysql.com today and try it out – we’re releasing this early version because we really want to hear your feedback.
Through geo-replication, had the ability to replicate entire cluster across data centers – for DR and data locality
Active/active, so both clusters can accept writes, then replication mechanisms detect and handle conflicts, so no passive resources Within the 7.2DMR, also have the ability to split a single cluster across data centers
48-core (96 CPU threads) HW. Table scans speed up more than PK access 8 LDM’s 8 Sysbench Tables 8 Partitions per table 6 Cluster connections
Transcript of "20140722 Taiwan MySQL User Group Meeting Tech Updates"