At Percona we provide services both Onsite - visiting the customers and Remote - logging in to their systems or communicating via email,phone,instant messaging.
We believe both approaches have their benefits and drawbacks and mixing them right way allows you to get your problems solved most efficient way.
[read more...]
Today we glad to announce release 1.0.3-4 of our XtraDB storage engine.
Here is a list of enhancements in this release:
Percona XtraDB 1.0.3-4 (Sakura) available in source and several binary packages.
XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.
Percona presented two talks at PHP Quebec last week - one on A Tour of MySQL High Availability, and another on Performance Tuning MySQL. There was a great reaction to showcasing some of the quick-wins that can be found by using the Percona patches. Unfortunately, the one thing that I forgot to mention in the slides is that the patches are Open Source and free to use.
We had too many requests for deb builds of Percona releases so I could not ignore that and added scripts to build binaries on our Ubuntu 8.10 box. It's going to be only 64bit releases (32bit is dead, isn't it?), and I tested binaries on Debian Lenny system and it seems working fine.
So I prepared binaries for our Build13 (which I actually did not announce to not spam PlanetMySQL a lot, I will figure out another channel for announcements), and you can get it there http://www.percona.com/mysql/5.0.77-b13/deb/, and your feedback is welcome!
As for changes for Build13 it contains InnoDB Data Dictionary restriction patch, which I mentioned before (http://www.mysqlperformanceblog.com/2009/02/11/limiting-innodb-data-dictionary/).
Speaking of deb binaries I tried to keep it compatible with native deb binaries, but I had to make some changes:
1. There was strange configure parameters
which I was not sure how to interpret, so I removed any mentioning of embedded server as 5.0 actually is not supposed to work in embedded mode and our patches can't be compiled in this case.
2. I removed NDB cluster engine from builds, we have not tested combination of our patches with NDB so I really do not know how it works together.
Enjoy!
Today we announce release 1.0.2-3 of our XtraDB storage engine.
Here is a list of enhancements:
Increasing the number of rseg may be helpful for CPU scale of write-intentional workloads. See benchmark results.
As you know, the group commit of InnoDB doesn't work after MySQL 5.0 with binlog.
We pretend to fix this and added "innodb_enable_unsafe_group_commit=[0|1]" parameter. Note if you set this parameter to "1" record order of binlog and InnoDB transaction log could be not same. But because InnoDB manages transactions in correct order most users may not have problem with this.
Percona XtraDB 1.0.2-3 (Sapporo) available in source and several binary packages.
XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.
Percona is hiring. We've added several experts recently and we're growing at a fast but sustainable pace. The demand for our services is strong, and we have openings for more experts in the next couple of months.
Let me explain a little about what we're looking for at the moment. While we do have a career path for less experienced people, right now we are looking for people who are top-level, senior experts in LAMP/Open-Source performance and scalability. Most of our work involves MySQL (at least peripherally, usually centrally) but not all of it; and we are looking for a PostgreSQL expert as well as systems administration and operations skills. If you're also an expert in a related technology (e.g. Hadoop, popular cloud platforms, or some other component that you might expect to see at the Percona Performance Conference) we'd like to talk with you.
All of us here at Percona warmly invite you to Percona Performance Conference 2009 on April 22 and 23, 2009 in the Hyatt Regency in Santa Clara, California. The theme for the conference is Performance Is Everything. This conference is about application performance overall, not just databases. Attendance is free of charge for everyone. Experts in many types of technologies -- databases, search, cloud computing, massively parallel computing, client-side optimization -- will present their real-life experience.
As we've said before, the Percona team just keeps growing. This time around, I'm pleased to welcome Ryan and Vladimir.
Ryan Lowe initially joined us from Florida (USA) in June. In his previous lives he scaled an Alexa top 1000 site with a sharded MySQL backend, worked in aerospace, worked in telecom, and lots of other things. His background as a consultant, DBA (with Oracle, too!), DBA manager, and programmer makes him a great match for Percona's clients. He also contributed some improvements to Wordpress, and he blogs here and on Pablowe.
Vladimir Fedorkov joins us from Lipetsk in the Russian Federation. (Brrr!) Vladimir and Peter have known each other and worked together for years in past endeavors. Vladimir can make Sphinx do just about anything, and is an expert systems administrator too. (Did you know that we provide systems administration services to our clients? It's not all about query optimization.) Vladimir is also the leader of one of our groups of consultants (codename: Mercury) and is helping us solidify core parts of our services offerings.
Vladimir and Ryan, a big welcome -- we are fortunate indeed you're working with us. And... go team!
PS: I can't help but triple-dip, and point out that our own Ewen Fortune has been a MySQL Cluster Certified DBA for quite a long time now. OK, shameless plug over. And, congratulations Nicklas!
Percona has been building and contributing to open-source software since the company was founded, and individually we've been doing the same thing for many years. We think it's a huge value for our customers and the community.
We're involved in a dozen or so open-source projects, but our three core efforts at the moment are the following:
We have a team of dedicated MySQL developers working on the server and on ExtraDB, and a dedicated Maatkit developer. Other Percona employees also put significant time into these projects.
Outside observers have commented that our development process doesn't seem very open-source. That is, we typically just go build the software and then announce it. We don't involve the community very much in our decisions about what features to include, or how they should get built; and we don't encourage community contributions directly into our codebase. There's also some ambiguity about where the money comes from and where it goes. These are all fair points to bring up. Peter, Vadim and I thought we should address them and let everyone know how we really work on these things and what our vision for the future is.
Today we announce release 1.0.2-2 of our XtraDB storage engine.
Here is a list of enhancements:
The patch splits global InnoDB buffer_pool mutex into several and eliminates waitings on flush IO and mutex when there is no enough free buffers. It helps if you have performance drops when data does not fit in memory.
InnoDB has a concurrent transaction limit of 1024 because in the standard InnoDB the number of undo slots is fixed value. This patch expands the maximum number of undo slots to 4072 and allows better utilizing modern hardware. (Thank SmugMug for this feature!)
ATTENTION: If the option was enabled and the expanded slots are used, you cannot use the datafile with system tablespace for the software which assume 1024 slots (e.g. the other mysqld or innodb hotbackup). See documentation for details.
Percona XtraDB 1.0.2-2 available :
XtraDB is compatible with existing InnoDB tables (Warning: unless you used innodb_extra_undoslots ) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona's current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.
del.icio.us
digg