What's New in MySQL 8.0 @ HKOSC 2017

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |
https://www.facebook.com/groups/hkmysqlusergroup/

What's New in MySQL 8.0
HKOSCon 2017
Ryusuke Kajiyama / 梶山隆輔
MySQL Global Business Unit
MySQL Sales Consulting Senior Manager, Asia Pacific & Japan

Safe Harbor Statement
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 Innovation: 5.7 -> 8.0
- 3x Better Performance
- Replication Enhancements
- Optimizer Cost Model
- JSON Support
- Improved Security
- Sys & Performance Schema
- GIS
MySQL 5.7 (GA)
MySQL InnoDB Cluster (GA)
- MySQL Group Replication
- MySQL Router
- MySQL Shell
MySQL 8.0 (DMR)
- Data Dictionary
- Roles
- Unicode
- CTEs
- Window Functions
- Security
- Replication
- SysSchema
- GIS

100%
6
Virtually all organizations require
their most critical systems to be
highly available

InnoDB Cluster
7
App Servers with
MySQL Router
MySQL Group Replication
MySQL Shell
Setup, Manage,
Orchestrate
“High Availability becomes a core
first class feature of MySQL!”
GA

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 8
MySQL InnoDB Cluster: Vision
“A single product — MySQL — with high availability and scaling
features baked in; providing an integrated end-to-end solution
that is easy to use.”

• One Product: MySQL
– All components created together
– Tested together
– Packaged together
• Flexible and Modern
– SQL and NoSQL together
– Protocol Buffers
– Asynchronous API
– Developer friendly
9
• Easy to Ue
– One client: MySQL Shell
– Easy packaging
– Integrated orchestration
– Homogenous servers
• Support Read/Write Scale Out
– Sharded clusters
– Federated system of N replica sets
• Supporting cross shard operations
– Each replica set manages a shard
MySQL InnoDB Cluster: Goals

MySQL Powers the Web
10

Evolution Driving Roadmap: 1995 vs 2017
There was no
local. Now
everything is
contextual to
me as a user.
The internet was
global, but full of
silos. Now we are
more connected
than ever.
In the past APIs
were cumbersome,
powered by SOAP
and XML-RPC.
There is now an
increased focus on
privacy and
protecting
information.

• Switched to
Boost.Geometry
library
• R+Tree Indexes for
InnoDB
• Spatial Types for
InnoDB
• Optimized InnoDB
Temporary Tables
• Optimized Packed
Sort Buffer
• Switched InnoDB to
DYNAMIC row format
by default
• Native JSON Data
Type
• 20+ JSON Functions
• Generated Columns
for Functional Index
• JSON Comparator
• Short-hand JSON
operators
• Secure by Default
• Password Expiry
• Password Policy
• Remove old
password hash
• Encrypted
Tablespaces, TDE
(Enterprise)
• Firewall (Enterprise)
• Audit (Enterprise)
12
Evolution Driving Roadmap: MySQL 5.7 Recap

• Geography support
• Spatial Reference
Systems (SRS)
Support
• SQL/MM Information
Schema views
• Standard compliant
axis ordering in
import/export
functions
• Utf8mb4 as default
• Up to 16x Faster
Performance
• Based on Unicode 9.0
• New collations with
Accent/Case
sensitivity
• Japanese Collation
• Aggregate, table and
Pretty print
Functions
• Sort Performance
Improvements
• Optimizer support for
in-place update
• JSON Shell
• Roles
• Encrypted REDO Logs
and UNDO space
• Finer grained system
privileges
• Atomicity in Privilege
statements
13
Evolution continued in MySQL 8.0

0
45000
90000
135000
180000
8 16 64 128 512 1024
SELECT DISTINCT_RANGES
0
10000
20000
30000
40000
8 16 64 128 512 1024
OLTP RO
0
7500
15000
22500
30000
8 16 64 128 512 1024
OLTP RW
MySQL 8.0 vs MySQL 5.7 utf8mb4
+300-350% in OLTP RO
+176-233% in OLTP RW
+1500-1800% in SELECT DISTINCT_RANGES

• Increased Reliability
• Built on InnoDB
– No FRM files
– No DB.OPT files
– No TRG files
– No TRN files
– No PAR files
– MyISAM not required
• Atomic DDL
– Better Replication
– Simplifies server edge cases
• MDL for Foreign Keys
• Flexible Metadata API
– Easier path to adding new features
• Better cross-platform experience
– No dependencies on filesystem
semantics
15
MySQL 8.0: Native Data Dictionary

MySQL Data Dictionary before MySQL 8.0
Data Dictionary
Files
FRM TRG OPT
System Tables (mysql.)
user procevents
InnoDB System Tables
MyISAM
File system
InnoDB
SQL

Transactional Data Dictionary in MySQL 8.0
Data Dictionary
InnoDB
SQL
DD TableDD TableDD Table

New! MySQL Roles
Improving MySQL Access Controls
• Introduced in the 8.0.0 DMR
• Easier to manage user and applications rights
• As standards compliant as practically possible
• Multiple default roles
• Can export the role graph in GraphML
18
Feature Request
from DBAs
Directly
In directly
Set Role(s)
Default Role(s)
Set of
ACLS
Set of
ACLS

New! InnoDB Redo and Undo Encryption
• AES 256 encryption
• Encrypted when redo/undo log data is written to disk
• Decryption occurs when redo/undo log data is read from disk
• Once redo/undo log data is read into memory, it is in unencrypted form.
• Two tiered encryption – like Innodb tablepace encryption
– Fast key rotation, high performance
• Easy to use
– Enabled using innodb_redo_log_encrypt and innodb_undo_log_encrypt
19
Feature Request
from DBAs

MySQL 8.0: Boosts Developer Productivity
• New! CTEs and Recursive CTEs
• New! Window Functions
• New! SKIP LOCKED and NOWAIT
• UUIDs and Bitwise Functions
20

Hierarchy Traversal
21
Employee database
CREATE TABLE employees (
id INT PRIMARY KEY,
name VARCHAR(100),
manager_id INT,
FOREIGN KEY (manager_id)
REFERENCES employees(id) );
INSERT INTO employees VALUES
(333, "Yasmina", NULL), # CEO
(198, "John", 333), # John reports to 333
(692, "Tarek", 333),
(29, "Pedro", 198),
(4610, "Sarah", 29),
(72, "Pierre", 29),
(123, "Adil", 692);

Hierarchy Traversal
22
List reporting chain
WITH RECURSIVE
emp_ext (id, name, path) AS (
SELECT id, name, CAST(id AS CHAR(200))
FROM employees
WHERE manager_id IS NULL
UNION ALL
SELECT s.id, s.name,
CONCAT(m.path, ",", s.id)
FROM emp_ext m JOIN employees s
ON m.id=s.manager_id )
SELECT * FROM emp_ext ORDER BY path;
id name path
333 Yasmina 333
198 John 333,198
692 Tarek 333,692
29 Pedro 333,198,29
123 Adil 333,692,123
4610 Sarah 333,198,29,4610
72 Pierre 333,198,29,72

Window function example
23
PARTITION == disjoint
set of rows in result set
name dept_id salary dept_total
Newt NULL 75000 75000
Dag 10 NULL 370000
Ed 10 100000 370000
Fred 10 60000 370000
Jon 10 60000 370000
Michael 10 70000 370000
Newt 10 80000 370000
Lebedev 20 65000 130000
Pete 20 65000 130000
Jeff 30 300000 370000
Will 30 70000 370000
Sum up total salary for each department:
SELECT name, dept_id, salary,
SUM(salary) OVER (PARTITION BY
dept_id) AS dept_total
FROM employee
ORDER BY dept_id, name;
The OVER keyword
signals a window function

MySQL 8.0: Better Handing of Hot Rows
SELECT seat_no
FROM seats
JOIN seat_rows USING ( row_no )
WHERE seat_no IN (3,4)
AND seat_rows.row_no IN (12)
AND booked = 'NO'
FOR UPDATE OF seats SKIP LOCKED
FOR SHARE OF seat_rows NOWAIT;
Non deterministically
skip over locked rows
Error immediately
if a row is already
locked
Feature Request
from Developers

MySQL 8.0: Makes Managing Scale Easier
• Greater density per server
• Operator Friendliness
• Increased Reliability
• New! Improved Replication Throughput
25

• Storage engines:
– Estimate for how much of data and
indexes are in a memory buffer
– Estimate for hit rate for memory buffer
• Optimizer cost model:
– Take into account whether data is
already in memory or need to be read
from disk
Memory Buffer Aware Cost Estimates
Server
Storage
engine
Disk data
Query
executor
Database
buffer

MySQL 8.0: Performance Schema
• SQL error instrumentation
• Indexes
• Configuration Variables
• New! Data Locks
• New! Histograms
27

Performance Comparison
28
0. 10. 20. 30. 40.
Query Time MySQL 8.0
MySQL 5.7
Over 30x faster!
SELECT * FROM sys.session
1000 active sessions
Time in Seconds (Lower is better)

MySQL 8.0: Invisible Indexes
• Indexes are “hidden” to the MySQL Optimizer
– Not the same as “disabled indexes”
– Contents are fully up to date and maintained by DML
• Two use cases:
– Soft Delete (Recycle Bin)
– Staged Rollout
29
Feature Request
from DBAs

MySQL 8.0: Persist Configuration
• Persist GLOBAL Server Variables
– SET PERSIST max_connections = 500;
• Examples Include:
– Offline_mode
– Read_Only
• Requires no filesystem access
• New! Captures timestamp and change user
30
Cloud Friendly

All these features plus…
• Source code now documented with
Doxygen
• Plugin Infrastructure!
• Expanded GIS Support
• Expanded Query Hints Support
• Improved Scan Query Performance
• Improved BLOB Storage
• Improved Memcached Interface
• Cost Model Improvements
• Scalability Improvements
• Atomicity in Privileges
• Parser Refactoring
• Improvements to Temporary Tables
• C++11 and Toolchain Improvements
• GTID_PURGED always settable
• Persistent Auto Increment
• Native InnoDB Data dictionary
• Improved Information Schema performance
• New! SQL Grouping Function
• New! Optimizer Trace detailed sort statistics
• New! Descending Indexes
• New! Smaller Package Downloads
• New! JSON Aggregate, Pretty print functions
• New! JSON performance improvements
• New! Expanded Query Hints
• New! Improved usability of cost constant
configuration
• Group Replication in 8.0
• New! Transaction Save Point support in
Group Replication
• New! Improved Replication Applier Lag
Statistics in Performance Schema
• New! Per Multi-source Channel Replication
Filters
• New! Atomic DDL extended to the Binary
Log
• New! Performance Improvements on the
Replication Applier
• New! Parallel Replication Applier Policy
• New! Binary Log Management
Enhancements
• New! Additional Metadata Into the Binary
Log

What's New in MySQL 8.0 @ HKOSC 2017

What's New in MySQL 8.0 @ HKOSC 2017

More Related Content

What's hot (20)

Similar to What's New in MySQL 8.0 @ HKOSC 2017 (20)

More from Ivan Ma (13)

Recently uploaded (20)

What's New in MySQL 8.0 @ HKOSC 2017