It’s been a little while since I blogged on MySQL on POWER (last time was thinking that new releases would be much better for running on POWER). Well, I recently grabbed the MySQL 5.6.20 source tarball and had a go with it on a POWER8 system in the lab. There is good news: I now only need one patch to have it function pretty flawlessly (no crashes). Unfortunately, there’s still a bit of an odd thing with some of the InnoDB mutex code (bug filed at some point soon).
But, with this one patch applied, I was getting okay sysbench results and things are looking good.
Now just to hope the MySQL team applies my other patches that improve things on POWER. To be honest, I’m a bit disappointed many of them have sat there for this long… it doesn’t help build a development community when patches can sit for months without either “applied” or “fix these things first”. That being said, just as I write this, Bug 72809 which I filed has been closed as the fix has been merged into 5.6.22 and 5.7.6, so there is hope… it’s just that things can just be silent for a while. It seems I go back and forth on how various MySQL variants are going with fostering an external development community.
MySQL 5.6.20 on POWER: Itâ€™s been a little while since I blogged on MySQL on POWER (last time was thinking that… http://t.co/BxAJwaGw5s
New #mysql planet post : MySQL 5.6.20 on POWER http://t.co/MGOFz1sEep
MySQL 5.6.20 on POWER http://t.co/AzpRFSuzWZ
Hi, have you tried these patches on MariaDB 10 at all with xtradb? You would probably find uptake of your patches to be much faster.
Maybe Percona or MariaDB becomes the Power distribution of choice.
Where is Power HW for MariaDB and Percona to do debugging and perf testing? I know there is at least one server at Oregon State Open Source Lab (OSU OSL) that have been used by PostgreSQL.
MariaDB 10.0 contains a bunch of patches to work on POWER. I expect to write about it at some point soon.