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
