In this Percona Live 2018 blog, we’ll talk with Ronald Francisco, SRE of Database Infrastructure at Twitter about why they moved from a fork of MySQL to MySQL 5.7.

We already started today with a great set of keynote sessions, and now the breakout sessions have begun in earnest. I’ve been looking in on the talks and stopping to talk with some of the presenters.

In this session, Ronald Ramon Francisco (Twitter Inc) SRE, Database Infrastructure presented the motivation for moving from a fork to MySQL to MySQL proper, and why they decided to do it. Twitter has been using their own fork of MySQL for many years. Last year the team decided to migrate to the community version of MySQL 5.7 and abandoned their own version. The road to the community version was full of challenges.

He also discussed the challenges and surprises encountered and how they overcome them. Finally, He looked at lessons learned, …

Last year we already published our over 2.1M QPS record with MySQL 8.0 -- it was not yet GA on that moment and the result was obtained on the server with 4CPU Sockets (4S) Intel Broadwell v4. We did not plan any improvement in 8.0 for RO related workloads, and the main target of this test was to ensure there is NO regressions in the results (yet) comparing to MySQL 5.7 (where the main RO improvements were delivered). While for MySQL 8.0 we mostly focused our efforts on lagging WRITE performance in MySQL/InnoDB, and our "target HW" was 2CPU Sockets servers (2S) -- which is probably the most widely used HW configuration for todays MySQL Server deployments..
However, not only SW, but also HW is progressing quickly these days ! -- and one of my biggest surprises last time was about Intel Skylake CPU ;-)) -- the following graph is …

Welcome to Percona Live 2018 keynotes, day one!

Percona Live 2018 is up and running! We call this day one, but in reality, yesterday was filled with tutorials that provided excellent and practical information on how to get your MySQL, MongoDB, MariaDB and PostgreSQL environments up, running and optimized.

Today we started with keynote presentations from Percona, a technology panel, Oracle and Netflix. You can view the recording of today’s keynotes here.

Percona Welcome

Laurie Coffin (Percona)

…

Last week, Oracle announced the general availability of MySQL 8.0. This is good news for database users, as it means Oracle is still developing MySQL.


I decide to celebrate the event by doing a quick test of MySQL 8.0. Here follows a step-by-step description of my first experience with MySQL 8.0.
Note that I did the following without reading the release notes, as is what I have done with every MySQL / MariaDB release up to date; In this case it was not the right thing to do.

I pulled MySQL 8.0 from ghit@github.com:mysql/mysql-server.git
I was pleasantly surprised that 'cmake . ; make' worked without without any compiler warnings! I even checked the used compiler options and noticed that MySQL was compiled with -Wall + several other warning flags. Good job MySQL team!

I did have a little trouble finding the mysqld binary as Oracle had moved it to …

MySQL 8.0.2 introduced a small yet powerful per transaction metadata information containing the transaction length in binary logs.

MySQL binary logs are being used for many other things than MySQL replication or backup/recovery: replicate to Hadoop; replicate to other databases, such as Oracle; capture data change (CDC) and extract-transform-load (ETL); record change notification for cache invalidation; change tracking for differential backups; etc.…

This week, Percona partners with Microsoft and Mesosphere to make it easier for organizations to take advantage of cloud and container environments and run their open source databases, ensuring optimal performance while shifting their focus to improving applications and better supporting the business.

Percona’s new partnership with Microsoft to support Microsoft Azure customers, along with the availability of Percona Server for MongoDB in the Mesosphere DC/OS community, reflect Percona’s commitment to providing comprehensive support for open source databases in cloud deployments. 

With open source databases now standard in the enterprise, organizations are increasingly looking to deploy those databases in public cloud environments to benefit from the flexibility, …

Percona announces the GA release of Percona Server for MySQL 5.7.21-21 on on April 24, 2018. Download the latest version from the Percona web site or the Percona Software Repositories. You can also run Docker containers from the images in the Docker Hub repository.

This version of Percona Server for MySQL 5.7.21 includes three new encryption features – Vault keyring plug-in, encryption for InnoDB general tablespaces, and encryption for binary log files.

These new capabilities, which allow companies to immediately …

Percona announces the GA release of Percona XtraBackup 2.4.11 on April 24, 2018. This release is based on MySQL 5.7.19. You can download it from our download site and apt and yum repositories.

Percona XtraBackup enables …

MySQL InnoDB Cluster has proven with the first GA release its potential as the native out-of-the-box HA solution for MySQL. With the second GA release, usability, stability and flexibility were greatly improved as described in the previous blog post.

This tutorial aims to show how does a typical InnoDB cluster setup look like and how that setup even became simpler and more effective as before.…

MySQL 8.0 has a rich set of features. One of the feature which interests DBA’s more is invisible index

What is an index in MySQL ?

• The indexes are used to find rows with specific column values quickly. Without an index, MySQL must begin with the first row and then read through the entire table to find the relevant rows.

What is invisible index ?

• The invisible index is ability to mark an index as unavailable for use by optimizer.
• In MySQL 5.7 and other previous versions the indexes are visible by a default.
• To control the index visibility for a new index ,use a  visible or invisible key words as a part of the index creation.

How to add a invisible index on existing table ?

Syntax :