Percona Server version 5.6.16-64.0
Based on MySQL 5.6.16, including all the bug fixes in it, Percona Server[Read more...]
|Showing entries 1 to 30 of 83||Next 30 Older Entries|
Percona Server version 5.5.36-34.0
Percona is glad to announce the release of Percona Server 5.5.36-34.0 on March 10th, 2014 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.36, including all the bug fixes in it, Percona Server 5.5.36-34.0 is now the current stable release in the 5.5 series. All of Percona‘s[Read more...]
Percona Server version 5.6.16-64.0 with TokuDB engine
Based on Percona Server 5.6.16-64.0 including all the features and bug fixes in it, and on TokuDB 7.1.5-rc.3,[Read more...]
A couple of weeks ago, shortly after Vadim wrote about Percona Cloud Tools and using Slow Query Log to capture the data, Mark Leith asked why don’t we just use Performance Schema instead? This is an interesting question and I think it deserves its own blog post to talk about.
First, I would say main reason for using Slow Query Log is compatibility. Basic Slow query log with microsecond query time precision is available starting in MySQL 5.1, while[Read more...]
We just published results with improvements in Thread Pool in Percona Server:
Percona Server: Thread Pool Improvements for Transactional Workloads
Percona Server: Improve Scalability with Thread Pool
What I am happy to see is that Percona Server is able to handle a tremendous amount of user connections. From our charts you can see it can go to 16000 active connections without a decline in throughput.[Read more...]
Percona is pleased to announce the first General Availability release of the leading open source High Availability solution for MySQL, Percona XtraDB Cluster 5.6 on January 30, 2014. Binaries are available from downloads area or from our software repositories.
Percona XtraDB Cluster 5.6
Percona XtraDB Cluster 5.6 is an active/active cluster solution for High Availability (HA) MySQL that delivers performance and
In a previous thread pool post, I mentioned that in Percona Server we used an open source implementation of MariaDB’s thread pool, and enhanced/improved it further. Below I would like to describe some of these improvements for transactional workloads.
When we were evaluating MariaDB’s thread pool implementation, we observed that it improves scalability for
AUTOCOMMIT statements. However, it does not scale well with multi-statement transactions. The
UPDATE_NO_KEY test which was run as an
AUTOCOMMIT statement and inside a transaction gave the following results:
By default, for every client connection the MySQL server spawns a separate thread which will process all statements for this connection. This is the ‘one-thread-per-connection’ model. It’s simple and efficient until some number of connections N is reached. After this point performance of the MySQL server will degrade, mostly due to various contentions caused by N threads that are trying to access shared resources: either system ones like CPU, IO, memory or MySQL specific: structures/locks/etc. To keep the system stable and avoid degradation in the performance we need to limit the number of active threads, and at the same time we do not want to limit number of the client connections. The ‘Thread Pool’ model helps us to achieve that. It allows mapping N client connections to M number of active threads (actually[Read more...]
Percona Server version 5.5.35-33.0
Percona is glad to announce the release of Percona Server 5.5.35-33.0 on December 20th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.35, including all the bug fixes in it, Percona Server 5.5.35-33.0 is now the current stable release in the 5.5 series. All of Percona‘s[Read more...]
I recently conducted a test backup of my “master-slave” setup in my VirtualBox as I was migrating from Percona Server 5.6.12 to version 5.6.13-rel61.0 with Percona XtraBackup v2.2.0 rev. 4885. However, doing the backup on my slave, I encountered this problem:
 Compressing and streaming ./test/checksum.ibd  Compressing and streaming ./mysql/slave_master_info.ibd Assertion "to_read % cursor->page_size == 0" failed at fil_cur.cc:293 innobackupex: Error: The xtrabackup child process has died at /usr/bin/innobackupex line 2641.
This is related to a bug posted by my colleague[Read more...]
Recently, I helped a client that was having issues with deployments causing locking in their production databases. At a high level, the two key components used in the environment were:
At a high level, they currently used a CLI call to Liquibase as a sub-task within a larger deployment task. The goal of this engagement was to modify that sub-task to run Liquibase in a non-blocking fashion as opposed to the default that just runs native ALTERS against the database.
As I wasn’t very familiar with Liquibase, I took this opportunity to learn more about it and it seems like a very valuable tool.[Read more...]
8PM. One of the servers found a critical bug. Hop online and discuss, log bug. 10PM. Patch ready. 10:30PM. New build ready. 10:45PM. New RQG run initiated. This was by no means an uncommon sight during the months of testing that went into Percona Server 5.6, in fact it was commonplace.
At a certain point, we had 3 very high end servers (modern cpu’s, heaps of cores and memory), all equipped with either fast SSD’s or Fusion-io flash storage, executing thousands of trials, 8 in parallel per server, each executing 1 to 25 mysql threads per running mysqld instance.
And that was just the final months of testing. Before that much work was done on finding “every last bug out there”. We discovered many bugs in both upstream (Oracle’s MySQL 5.6) and in Percona Server 5.6. I personally logged around 100[Read more...]
Percona Server has implemented per-query variable statement support in version 5.6.14-62.0. This feature provides the ability to set variable values only for a certain query, after execution of which the previous values will be restored. Per-query variable values can be set up with the following command:
mysql> SET STATEMENT <variable=value> FOR <statement>;
If we want to increase the sort_buffer_size value just for one specific sort query we can do it like this:
mysql> SET STATEMENT sort_buffer_size=100000 FOR SELECT name FROM name ORDER BY name;
In MySQL 5.6 InnoDB has a dedicated thread (page_cleaner) that’s responsible for performing flushing operations. Page_cleaner performs flushing of the dirty pages from the buffer pool based on two factors:
- access pattern - the least recently used pages will be flushed by LRU flusher from LRU_list when buffer pool has no free pages anymore;
- age – the oldest modified non-flushed pages are part of flush_list structure and will be flushed by flush_list flusher based on several heuristics.
Percona Server version 5.5.34-32.0
Percona is glad to announce the release of Percona Server 5.5.34-32.0 on October 28th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.34, including all the bug fixes in it, Percona Server 5.5.34-32.0 is now the current stable release in the 5.5 series. All of Percona‘s[Read more...]
Percona Server version 5.1.72-14.10
Percona is glad to announce the release of Percona Server 5.1.72-14.10 on October 28th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.72, including all the bug fixes in it, Percona Server 5.1.72-14.10 is now the current stable release[Read more...]
The technologies allowing to build highly-available (HA) MySQL solutions are in constant evolution and they cover very different needs and use cases. In order to help people choose the best HA solution for their needs, we decided, Jay Janssen and I, to publish, on a regular basis (hopefully, this is the first), an update on the most common technologies and their state, with a focus on what type of workloads suite them best. We restricted ourselves to the open source solutions that provide automatic failover. Of course, don’t simply look at the number of Positives/Negatives items, they don’t have the same values. Should you pick any of these technologies, heavy testing is mandatory, HA is never beyond scenario that have been tested.
A week ago we launched our first GA release of Percona Server 5.6 and it’s a real game-changer for us. The release of Percona Server 5.6 (our enhanced, drop-in replacement for MySQL) not only provides stability and performance but also provides key features only available in Oracle’s MySQL 5.6 Enterprise Edition. As usual, Percona Server 5.6 is 100 percent Free and Open Source Software.
On Oct. 16 I’ll lead a webinar that will present what’s new in Percona Server 5.6 that makes it the most powerful, highest performance, and most manageable free version of MySQL available today. The one-hour webinar starts at 1 p.m. Pacific time Wednesday. You can[Read more...]
Yesterday we announced the GA release of Percona Server 5.6, the latest release of our enhanced, drop-in replacement for MySQL. Percona Server 5.6 is the best free MySQL alternative for demanding applications. Our third major release, Percona Server 5.6 offers all the improvements found in MySQL 5.6 Community Edition plus scalability, availability, backup, and security features some of which are found only in MySQL 5.6 Enterprise Edition.
Percona Server 5.6 comes with:
Percona Server version 5.6.13-61.0
Based on MySQL 5.6.13, including all the bug fixes in it,[Read more...]
Percona Server provides users with a variety of powerful benefits including enterprise-grade features, high performance in demanding use cases, rich diagnostics, and access to unique Percona XtraBackup capabilities, all for free and open source. In addition, Percona Server is a drop-in MySQL replacement. Compatibility with MySQL has important ramifications (as well as some risks) as Giuseppe Maxia highlighted in a recent blog post about MySQL alternatives. Our commitment to drop-in compatibility with MySQL has important benefits for Percona Server users and drives our[Read more...]
Companies say they value the enterprise-grade features and high performance that Percona Server delivers for free and use the software to power critical business applications, hot new apps, and even a growing web host.
We’d love to hear from you. If you use Percona Server or our other software in a production environment,[Read more...]
I recently blogged on setting up Experimental Git mirror of Oracle MySQL trees up on GitHub. I’m now happy to announce that there are also mirrors for:
I’ve also updated the Oracle MySQL GIT mirror to include MySQL 5.7 and the (now abandoned) MySQL 6.0. I include the abandoned 6.0 tree as it can provide useful archaeology as to where some code came from.
I’d love to hear about any positive/negative experiences using these[Read more...]
One type of question we get very often (even in the form of filed bugs!) is how to switch from stock MySQL to Percona Server or switch from Percona Server 5.5 to Percona XtraDB Cluster using yum, but à la apt-get, i.e. having yum handle the replace.
In its simplest form, yum cannot replace a package¹ for another like apt-get does:
# yum -q -q install Percona-XtraDB-Cluster-server
Error: Percona-XtraDB-Cluster-server conflicts with Percona-Server-server-55
Error: Percona-XtraDB-Cluster-client conflicts with Percona-Server-client-55
While we are working hard on the final push of Percona Server 5.6 GA (I know that many people are waiting on this, but stay with us – we want to ensure that we have a quality release with great performance), I decided to make an experimental build of Percona Server 5.6 with the TokuDB engine.
It’s available here: http://www.percona.com/downloads/TESTING/Percona-TokuDB/.
If you are interested, please test it and provide us with feedback. If things look good, in couple months we may release an official Percona Server 5.6 with TokuDB.
The post[Read more...]
For performance reasons we are going to use SSD, and therefore there is a list of requirements for the architecture:
Looking on these requirements I actually think that TokuDB might be a good fit for this task.
Percona Server version 5.1.71-14.9
Percona is glad to announce the release of Percona Server 5.1.71-14.9 on August 27th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.71, including all the bug fixes in it, Percona Server 5.1.71-14.9 is now the current stable release in the[Read more...]
Percona Server version 5.5.33-31.1
Percona is glad to announce the release of Percona Server 5.5.33-31.1 on August 27th, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.33, including all the bug fixes in it, Percona Server 5.5.33-31.1 is now the current stable release in the[Read more...]
We receive this question about the ibdata1 file in MySQL very often in Percona Support.
The panic starts when the monitoring server sends an alert about the storage of the MySQL server – saying that the disk is about to get filled.
After some research you realize that most of the disk space is used by the InnoDB’s shared tablespace ibdata1. You have innodb_file_per_table enabled, so the question is:
|Showing entries 1 to 30 of 83||Next 30 Older Entries|