Percona Server for MySQL version 5.1.68-14.6
Percona is glad to announce the release of Percona Server 5.1.68 -14.6 on April 19, 2013 (downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.68, including all the bug fixes in it, Percona Server 5.1.68-14.6, a MySQL alternative, is now the current stable release in the 5.1 series. All …
[Read more]I don’t get to say this often, but “I’m hiring” (at Percona):
I’ve been with Percona for about 5 years, so I can tell you: it’s probably the best company to work at: great pay, great benefits, great people, and truly driven by a desire to do right by customers and do good work. What more can you ask for? Of course, all these jobs are MySQL-related: Perl + MySQL, PHP + MySQL–maybe the UI/UX job less so, but still close enough.
Instant Innodb, by Matt Reid
This book does a good job of explaining the InnoDB internals. I have found particularly useful the section where it describe in detail all the server variables affecting InnoDB. Although these variables are also in the MySQL manual, some of them have never been explained to me as thoroughly as this book as done.
The title claims that it is a InnoDB reference. If is more than that, as the reference part id covered in three chapters. The rest of the book gives useful advice on maintenance, monitoring, and troubleshooting.
Join in our Finnish ritual, next Friday, at the closing of MySQL & Cloud Database Solutions Day after Percona Live!
Just as information has become an integral part of technology, blogging has become an inseparable part of technology too. Database technologies are no exception and blogging in that arena is booming. This Log Buffer Edition is booming with some bombastic blog posts.
Oracle:
Arup Nanda asks. Application Design is the only Reason for Deadlocks? Think Again.
It’s time that businesses took a good, hard look at the way they manage their cloned database environments, Kyle Opines.
Randolf touches the interesting topic of ASM AU Size And LMT AUTOALLOCATE.
…
[Read more]Swapping has always been something bad for MySQL performance but it is even more important for HA systems. It is so important to avoid swapping with HA that NDB cluster basically forbids calling malloc after the startup phase and hence its rather complex configuration.
Probably most readers of this blog know (or should know) about Linux swappiness setting, which basically controls how important is the file cache for Linux. Basically, with InnoDB, since the file cache is not important we add “vm.swappiness = 0″ to “/etc/sysctl.conf” and run “sysctl -p” and we are done.
Swappiness solves part of the swapping issue but not all. With Numa systems, the picture is more complex and swapping can occur because of a memory imbalance between the physical cpus, the sockets and not cores. Jeremy Cole explained this here and …
[Read more]New 5.6.11 out
Introduction
This article will explain how the data is organized in InnoDB storage engine. First we will look at the various files that are created by InnoDB, then we look at the logical data organization like tablespaces, pages, segments and extents. We will explore each of them in some detail and discuss about their relationship with each other. At the end of this article, the reader will have a high level view of the data layout within the InnoDB storage engine.
The Files
MySQL will store all data within the data directory. The data directory can be specified using the command line option –data-dir or in the configuration file as datadir. Refer to the Server Command Options for complete details.
By default, when InnoDB is initialized, it creates 3 important files in the data directory – ibdata1, ib_logfile0 and …
[Read more]Looking for some substantial reading material as the days grow longer? You might consider dedicating a good chunk of time to review the MySQL 5.6.11 changelog. The MySQL Engineering team at Oracle has been busy, and it shows in this maintenance release. Stewart Smith recently noted the growth of the code base in 5.6 compared to 5.5. That may or may not be the best measure of productivity, but the number of fixed bugs in a maintenance release like 5.6.11 is sure a good indicator. A few general observations based on my quick study:
Following on from my fun post on Where are they now: MySQL Storage Engines, I thought I’d cover the few storage engines that are really just interfaces to a collection of things. In this post, I’m talking about MERGE.
The MERGE engine was basically a multiplexer down to a number of MyISAM tables. They all had to be the same, there was no parallel query execution and it saw fairly limited use. One of the main benefits was that then you could actually put more rows in a MyISAM table than your “files up to 2/4GB” file system allowed. With the advent of partitioning, this really should have instantly gone away and been replaced by it. It wasn’t.
It is another MySQL feature that exists likely due to customer demand at the time. It’s not a complete solution by any means, PARTITIONING is way more complete and …
[Read more]