Should I migrate from MySQL to Percona server
I have been experiencing dirty pages flushing problem in MySQL server. This occupies lot of CPU resources and my site becomes down because of lack of resources left in server. I got 10 Million records in database and it will grow further. My tables are running in innodb and since its transaction based site, I need innodb. Will migrating to Percona server remove my dirty pages flushing problem. Generally is it better to migrate or stick to MySQL?
Once I move to percona, if I want to revert back to Mysql can i restore the backup from percona to mysql?
Answer
Percona Server has many improvements to flushing. But on such a small database, it is likely that something is wrong, such as the buffer pool and log file size being at their defaults instead of configured for a production workload. I agree with other posters that you need to measure and understand the problem before trying something to see if it will solve it. I disagree that a migration to Percona Server needs to be regarded as a risky and time-intensive move, however. You can simply replace /usr/sbin/mysqld with the one you extract from Percona Server's tarball, and if you don't like it, put the old binary back. Percona Server is just MySQL with some non-disruptive improvements and you can be confident that switching to/from it will Just Work. (I work for Percona, by the way.)