June 19, 2013

Post: Is Synchronous Replication right for your app?

group? Results In both of the above examples you can imagine plenty of concurrent clients attempting to modify the same record at once.  But what will

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

to the point of ensuring transactions are copied to all nodes and global ordering is established, but apply and commitwill get to be a bit further behind applying. If you only write to a single node in PXC, then it is recommended you

Post: Percona's Commitments to MySQL Users

… about what Percona will do. We want to begin by saying “thank youto those …-long group effort from Monty, David, Marten and many others to develop …to increase your server count, instead of helping you make your systems more efficient. Conclusion We’re dedicated to advancing the state of the art in

Post: Pretending to fix broken group commit

in disk. So what can be wrong if you run –innodb-unsafe-group-commit — as I said there is possibility that transactions in binary-logs will be in different… do not urge to use –innodb-unsafe-group-commit, I propose to have BBU on your RAID. But if it appears you don’t have it…

Post: Group commit and real fsync

what is going on? Actually we’re looking at two issues here which interleave such funny way Group commit is broken inyour OS is not giving you real fsync you might not notice this bug. The performance degradation will still happen but it will

Post: Heikki Tuuri answers to Innodb questions, Part II

to the first file in a log file group. My questions are: What is always being written to the first file in the log file groupyou commit 1000 transactions per second, then you write 1000 times per second! A smart wear leveling should be able to cope with writes to

Post: MySQL 5.5.8 - in search of stability

…innodb_flush_log_at_trx_commit = 2 innodb_flush_method =… = 2000M innodb_log_files_in_group = 2 innodb_read_io_threads…, what will be the result if we try to increase it to 70%…you are killing your throughput. When you disable innodb_doublewrite, you can get stable throughput if you are lucky enough to

Post: When would you use SAN with MySQL ?

you better have binary log flushed on commit too. MySQL also has broken group commit (which we have partial fix for) meaning concurrent transaction commits willto directly attached storage too) is to really understand what you‘re trying to scale and analyze things appropriately. I’ve seen in

Post: Paul McCullagh answers your questions about PBXT

to your questions – as well as a few I gathered from other Percona folks, and attendees of OpenSQL Camp. Thank youIn the long run, this will determine to what extent we are able to continue to

Post: Heikki Tuuri Innodb answers - Part I

What are your suggestions here? HT: According to tests by Peter Zaitsev, O_DIRECT works well to remove double buffering. Inyou remove that mutex from 5.1, then InnoDB’s group commit works again. PZ: You can disable binary logging to get Group Commit