What MySQL-flavor to choose.
We are about to migrate from MySQL 4.1 to a 5.5 version. We heavily use InnoDB, have an dual quad Nahelem Xeon, 24GB DDR3, 4*SSD in RAID-10 on an Adaptec RAID with 512MB Cache and running under x64 Linux on a modern kernel. We replicate to several other slaves. I only have experience on vanilla MySQL-versions (compile my own). What flavor (MariaDB, MySQL, Percona) should i choose and why? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: What MySQL-flavor to choose.
On 2011-02-14 15:31, Singer X.J. Wang wrote: What is your load type? Heavy read but enough write not to benefit much from query cache. It is a webshop app (custom). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: What MySQL-flavor to choose.
On 2011-02-14 15:43, Singer X.J. Wang wrote: So I'm assuming OLTP type transaction, then I'm going to recommend MySQL 5.5. Why is that flavor to be chosen over MariaDB with XtraDB or Percona with XtraDB? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: What MySQL-flavor to choose.
According to the benchmarks on the Personal website, the 5.1 version of Persona has the same about performance as mysql 5.5 (http://www.percona.com/software/benchmarks/) Also the 5.5 version of the Persona(not reported as stable) is even better than mysql 5.5 according the the same site. Also after reading Dimitrik blog (http://dimitrik.free.fr/blog/archives/2010/07/mysql-performance-innodb-io-capacity-flushing.html), its seems to me , than one of the thing that are different between the stock mysql (5.5) and xtradb, is the way that they handle IO capacity and flush. So if you need to control the IO then you should use the stock mysql. My opinion is that both servers(personal 5.1 - mysql 5.5) , seem to be good enough for extreme workloads and they will do your job. Also (if it's an option) you can install both , and test them with a synthetic benchmark like sysbench. akops On 14/2/2011 4:34 μμ, Jay Ess wrote: On 2011-02-14 15:31, Singer X.J. Wang wrote: What is your load type? Heavy read but enough write not to benefit much from query cache. It is a webshop app (custom). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: What MySQL-flavor to choose.
Hi, Also after reading Dimitrik blog (http://dimitrik.free.fr/blog/archives/2010/07/mysql-performance-innodb-io-capacity-flushing.html), its seems to me , than one of the thing that are different between the stock mysql (5.5) and xtradb, is the way that they handle IO capacity and flush. So if you need to control the IO then you should use the stock mysql. Just to clarify, you can run with the same flushing algorithm under Percona server and the same io capacity options are available. http://www.percona.com/docs/wiki/percona-server:features:innodb_io#innodb_io_capacity The io_capacity feature actually came from the Google and Percona patches http://www.innodb.com/wp/products/innodb_plugin/license/third-party-contributions-in-innodb-plugin-1-0-4/ Cheers, Ewen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: What MySQL-flavor to choose.
According to http://dimitrik.free.fr/blog/archives/2010/12/mysql-performance-analyzing-perconas-tpcclike-workload-on-mysql-55.html the xtraDB is ignoring the io capacity setting. But this of course it might be just a minor bug in the percona version that dimitriK used in his test..:-) akops On 14/2/2011 7:16 μμ, Ewen Fortune wrote: Hi, Also after reading Dimitrik blog (http://dimitrik.free.fr/blog/archives/2010/07/mysql-performance-innodb-io-capacity-flushing.html), its seems to me , than one of the thing that are different between the stock mysql (5.5) and xtradb, is the way that they handle IO capacity and flush. So if you need to control the IO then you should use the stock mysql. Just to clarify, you can run with the same flushing algorithm under Percona server and the same io capacity options are available. http://www.percona.com/docs/wiki/percona-server:features:innodb_io#innodb_io_capacity The io_capacity feature actually came from the Google and Percona patches http://www.innodb.com/wp/products/innodb_plugin/license/third-party-contributions-in-innodb-plugin-1-0-4/ Cheers, Ewen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
