Last time this blog covered digging into a JSON document in a MySQL 5.7 table. The goal was to pull certain records matching a particular criteria. Both Peter Zaitsev and Morgan Tocker get my thanks for their kind comments. My example was a little contrived in that an application would be used to fine tune seeking for a particular key value pair. I was trying to pull single records which is kind of silly when it is much easier to use PHP to parse the data. What follows below is a sample PHP script to grab out the matching records and then feed the results, the JSON document, into an array.

#!/usr/bin/php
<?php
$mysqli = new mysqli("localhost", "root", "hidave", "test");

/* check connection */
if (mysqli_connect_errno()) {
    printf("Connect failed: %s\n", …

InnoDB in MySQL 5.7 introduced for the first time the ability to create a general tablespace and assign multiple tables to it.  These tablespaces can be assigned anywhere on the system.  They can even be assigned a smaller block size so that they can contain compressed tables that use that size as their key_block_size.…

This blog discusses how TokuDB impacts InnoDB performance when the two run in the same environment.

You would think MySQL storage engines are fairly independent of each other, even in the same environment. Enabling one, or changing its configuration, logically should have no impact on the performance of other engines (such as InnoDB) when they are accessing tables. The reality, however, is more complicated than that!    

Now that we’ve shipped TokuDB, we’ve been getting feedback from our community and customers that enabling TokuDB might negatively affect performance – even for queries that don’t touch TokuDB tables (and in some cases, even when TokuDB is kept completely idle).

In today’s simple article we will cover the steps needed for installing and configuring a basic LEMP stack on a openSUSE VPS. A LEMP stack is a synonym of LEMP server or LEMP web server. It refers to a set-up which includes Linux, Nginx, MySQL (MariaDB) and PHP. REQUIREMENTS We will be using our SSD 1 Linux VPS hosting plan for this tutorial. Log in to your server via SSH: # ssh root@server_ip Before starting, enter the command below to check whether you have the proper OS version installed on your machine: # cat /etc/issue which should give you the […]

Hello, all! Just a quick blog to remind you all about the Percona Live 2016 Community Game Night!

This awesome event is taking place on Wednesday, April 20 from 7:00 pm to 10:00 pm, after the Community Networking Reception. It’s modeled after last year’s extremely popular game night, featuring many of the same games back by popular demand:

• The Meltdown
• Segway Races
• Pac-Man Battle Royal!

This year we plan on tons more games compared to last year, with fun additions like a bowling alley and Oculus Rift experiences. We’ll have drinks, food and most importantly: some crazy good fun.

…

In this blog, we’ll discuss MicroSoft’s recent announcement that SQL Server will be available on Linux. If you’re going to Linux, why not move from SQL Server to MySQL?

The open source operating system Linux powers nearly one-quarter of all the servers running in Microsoft’s Azure cloud service. Until just last week, this meant nearly one-quarter of Azure cloud servers couldn’t actually run much Microsoft software.

So Microsoft is porting SQL Server to Linux. Currently, there is a private preview available with a planned full release sometime in mid-2017.  Microsoft …

Following earlier posts on replication and query cache improvements, this article will focus on a feature that can make Aurora more suitable for mission critical enterprise applications: near-instantaneous crash recovery.

While real-life performance is tricky to measure and may be evaluated differently in the context of different applications, downtime is a fairly straightforward thing to define and you most certainly want to avoid it regardless of what kind of service you're running. Let's take Aurora for a spin and see how it can make your life easier in this area.

Introduction This article doesn't pretend to be even remotely close to a proper technical description of MySQL startup and crash …

In this blog, I will answer questions posed in my recent introduction to MySQL troubleshooting basic techniques webinar.

Thank you for attending my March 10 MySQL troubleshooting webinar “Introduction to MySQL troubleshooting: basic techniques,” which is the second in the “MySQL Troubleshooting Webinar” series. The recording and slides for the webinar are available here. Here is the list of your questions that I wasn’t able to answer during the webinar, with responses.

Q: Any known …

This is the second and last tutorial blog post on how to use pt-table-checksum / pt-table-sync tools for MySQL replication.

In the first post, I showed you how to use the

pt-table-checksum

  /

pt-table-sync

  tools in a typical MySQL replication setup. In this post, we’ll discuss MySQL replication for more advanced topologies. I will show you how to use these tools in a chained …

Following the recent post on replication performance and efficiency, I'd like to talk about another MySQL feature that has received some treatment in Aurora: the Query Cache.
We'll first discuss the limitations of "traditional" Query Cache implementation, we will then watch a sysbench read-only test take off and go from 250K reads per second to nearly 650K reads per second, all thanks to the improved Query Cache. Have fun!
Query Cache The MySQL Query Cache is a hugely useful feature that caches the result sets of SELECT statements in memory. It makes perfect sense in typical OLTP applications (especially web apps), where queries are quite repeatable because the same piece of data is often selected multiple times by many clients.
The following performance issues are associated with query cache implementation in vanilla …