Google senior systems engineer Jeremy Cole is once again teaming with LinkedIn senior software engineer Davi Arnaut for two InnoDB-focused sessions at the upcoming Percona Live MySQL Conference and Expo 2014 this April 1-4 in Santa Clara, California. The duo will present “InnoDB: A journey to the core II” on April 2 and “InnoDB: A […]
Percona is glad to announce the first ALPHA release of Percona Server 5.6.16-64.0 with TokuDB engine on March 3rd, 2014. Downloads are available here and from the Percona Software Repositories. 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, Percona Server 5.6.16-64.0-tokudb is the first ALPHA […]
In my previous post I pointed out that the existing ARCHIVE storage engine in MySQL may not be the one that will satisfy your needs when it comes to effectively storing large and/or old data. But are there any good alternatives? As the primary purpose of this engine is to store rarely accessed data in disk […]
We’re looking for a full-time web back-end developer to join our team and help continue building the Percona Cloud Tools (https://cloud.percona.com) back end. We use the Go language, so we would love to find a Go programmer, but since Go is a very new language, we’re looking for any great programmer who wants to learn […]
Sometimes there is a need for keeping large amounts of old, rarely used data without investing too much on expensive storage. Very often such data doesn’t need to be updated anymore, or the intent is to leave it untouched. I sometimes wonder what I should really suggest to our Support customers. For this purpose, the […]
I am working on a customer’s system where the requirement is to store a lot of timeseries data from different sensors. For performance reasons we are going to use SSD, and therefore there is a list of requirements for the architecture: Provide high insertion rate Provide a good compression rate to store more data on […]
When executing an ALTER TABLE, InnoDB (and XtraDB) will create two InnoDB transactions: One transaction is created when the table being ALTERed is locked by the server. This will show up as something like “TABLE LOCK table schema.table_name trx id XXXX lock mode S” in SHOW ENGINE INNODB STATUS. Another is created when adding or […]
(This is a cross post from percona.tv – the home of percona material in video form.) Last month I gave a presentation at the PHP UK Conference on the InnoDB storage engine.Â I was a last minute speaker, and I want to thank them for the time-slot and their hospitality at short notice.
As part of our growth process and with the introduction of our Support and Maintenance services, we’re looking for a new Support Engineer.
You would be a part of a unit that operates 24×7 and be the first line of contact for our customers.
Responsibilities include handling or dispatching emergencies and support requests, triaging incoming issues, and ensuring customers always get the attention they need.
One of the big “Selling Points” of MySQL is support for Multiple Storage engines, and from the glance view it is indeed great to provide users with same top level SQL interface allowing them to store their data many different way. As nice as it sounds the in theory this benefit comes at very significant […]