We discuss INFORMATION_SCHEMA with plenty of examples on useful queries. In this week's Ear Candy, we talk about resident versus virtual memory on Linux, and in At the Movies has a video about MongoDB.
Events
DB Hangops in
May will be Wed May 8th and 22nd noon pacific time.
Upcoming MySQL tech tours
MySQL, the most popular open source database brings you great performance. You can see the performance details in http://dimitrik.free.fr/blog/. To help you get the most from MySQL's performance, take the MySQL for Performance Tuning course.
This four day instructor-led training course covers:
This course is available in three delivery types:
A little while ago I blogged about (and open sourced) an Impala-powered soccer visualization demo, designed to demonstrate just how responsive Impala queries can be. Since not everyone has the time or resources to run the project themselves, we’ve decided to host it ourselves on an EC2 instance. You can try the visualization; we’ve also opened up the Impala web interface, where you can see query profiles and performance numbers, and Hue (username and password are both ‘test’), where you can run your own queries on the dataset.
Deploying Impala on EC2
While there are …
[Read more]One of the main responsibilities of any database administrator is to keep a close eye on how database performance is impacting size and storage. Decisions will have to be made on whether or not to make changes within the database structure or application itself, or to make the changes on the storage and resource side [...] Read More
A default installation of MySQL is easy to perform, but if you really want your databases to sing, you should tune them like you would tune a piano. In MySQL tuning pertains to either the application or the database system. In this post, we cover some common tuning techniques and best practices to increase your [...] Read More
A few weeks ago I wrote about “MySQL Performance at High Concurrency” and why it is important, which was followed up by Vadim’s post on ThreadPool in Percona Server providing some great illustration on the topic. This time I want to target an opposite question: why MySQL performance at low concurrency is important for you.
I decided to write about this topic as a number of recent blog posts and articles look at MySQL performance starting with certain concurrency as the low point. For example, …
[Read more]Percona’s Kenny Gryp leads a recent MySQL workshop
Percona will be in Chicago and London the week of April 8th delivering two 2-day MySQL workshops. For our MPB readers, we are offering a 15% discount. Just use MPB15A when purchasing your tickets to one or both MySQL workshops.
This week we discuss changed behavior of variables in MySQL 5.6. In ear candy we talk about a cloud-based service to play with SQL on different databases, and At the Movies is Stewart Smith of Percona talking about MySQL in the Cloud as a Service during Linux Conf Australia in Canberra.
Changed behavior of variables in 5.6
boolean variables can be set to ON/OFF 1/0
TRUE/FALSE
Variables with changes:
log_slave_updates
With each release, the MySQL database brings you even better performance. To get the most from your MySQL servers, performance tuning is important. And what better route than to take the MySQL for Performance Tuning training course.
In this four-day instructor-led class you will learn to:
This course is available as:
Oracle has now launched MySQL-5.6.10-GA, so it is time to come up with some new benchmark results. The test candidates in this benchmark run are
The 5.5 versions are in because I wanted to check for any regressions. In the past we have often seen performance regressions in newer versions which were caused by new features.
This time the benchmark was run on a different box. The main difference is that this box does not have SSD but a high performance RAID-5 with 512M of battery-backed cache. Besides that the machine has 16 cores out of which 12 were used for mysqld and the other 4 for sysbench.
The benchmark uses sysbench-0.5 OLTP with 8 tables and 10G worth of data. InnoDB buffer pool was 16G, InnoDB log group capacity 4G (the maximum for MySQL-5.5). The different disk system required different InnoDB …
[Read more]
