After many months of heavy development and testing, Debian 8 (Jesse) and Ubuntu 15.04 (Vivid Vervet) were released recently. For those who already upgraded their systems and/or plan do do it in close future, we prepared builds of WebScaleSQL :-) http://repo.psce.com/download/webscalesql/deb/x86_64/vivid/ http://repo.psce.com/download/webscalesql/deb/x86_64/jessie/ You can also install it using PSCE repository. … [Read more...] about WebScaleSQL builds available for Debian 8 and Ubuntu 15.04
On Tuesday Steaphan Greene announced that all currently-pushed changes have now been rebased onto the newly-released upstream MySQL-5.6.24. … [Read more...] about WebScaleSQL 5.6.24 is built and ready to test
Driven by popularity of previous post about Debian/Ubuntu builds of WebScaleSQL and long discussions during FOSDEM conference this weekend, PSCE engineering team decided to put even more effort into. … [Read more...] about WebScaleSQL RPMs available at PSCE repository
We have been looking at the WebScaleSQL project with great excitement. As with any new enhancements to the MySQL world, we need to test extensively to ensure we can give PSCE customers the best advice possible. Since this project is source only, we decided to add WebScaleSQL builds to our repo, so we could examine the changes being introduced by all the different collaborators. … [Read more...] about WebScaleSQL builds for the MySQL Community
Long running transactions can be problematic for OLTP workloads, particularly where we would expect most to be completed in less than a second. In some cases a transaction staying open just a few seconds can cause behaviour that is entirely unexpected, with the developers at a loss as to why a transaction remained open. There are a number of ways to find long running transactions, luckily versions of MySQL from 5.6 onwards provide some very insightful instrumentation. … [Read more...] about Tracking MySQL query history in long running transactions
I had to benchmark an EC2 instance to see whether a database could be safely moved to it. It is a good practice, which helps avoiding surprises when an instance or its storage are allocated in a noisy neighborhood, where the neighbors use so much resources that it affects the performance of our MySQL database. It is understandable that one can never get very reliable results on EC2, this is a shared environment after all, and that some fluctuations should be expected, however it is still good to know the numbers. I started my benchmarks and everything seemed fine at first, but then sometimes statistics I was getting started looking quite odd. … [Read more...] about Interesting behavior of a MySQL benchmark on EC2
In one of my previous posts, "How to resize InnoDB logs?", I gave the advice on how to safely change the size of transaction logs. This time, I will explain why doing it may become necessary. … [Read more...] about What is the proper size of InnoDB logs?