June 19, 2013

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

Transactions Identifiers are one of the new features regarding replication in MySQL 5.6. They open up …topology. However you should keep in mind some limitations of the current implementation. This post is the…the master read-only. However, “at the same time” means “at the same binlog position”, so …

Post: More on MySQL transaction descriptors optimization

MySQL transactiontransactions optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is quite limited

Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2

transactions, while a great optimization in itself, applies only to the following kinds of transactions: MySQL transactions started with START TRANSACTION READ ONLY MySQL transactionsMySQL 5.6 to achieve even better scalability while removing the read-only limitations

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

limit defaults to 16 transactions. This effectively means that this is as far as a given node can be behind committing transactions…cluster might be: mysql> set global wsrep_provider_options=”gcs.fc_limit=500; gcs…replication conflicts more likely and therefore time-consuming to the application. How …

Post: Is Synchronous Replication right for your app?

… want this transaction to persist after a crash, it has to get to disk. This has no effect on standard MySQL replication… the number of times specified by this variable (default is 1 retry).  This means more waiting, and after the limit is exceeded you will still get the deadlock error. This is not implemented for full BEGIN … COMMIT multi-statement transactions

Post: Ultimate MySQL variable and status reference list

time_formatblogpercona.commanual time_zoneblogpercona.commanual timed_mutexesblogpercona.commanual timestampblogpercona.commanual tmp_table_sizeblogpercona.commanual tmpdirblogpercona.commanual transaction_alloc_block_sizeblogpercona.commanual transaction_isolationblogpercona.commanual transaction

Post: How to debug long-running transactions in MySQL

… long-running transaction. If a transaction remains open for a very long time without committing, and has modified data, then other transactions could block… JOIN information_schema.processlist p on b.trx_mysql_thread_id = p.ID LIMIT 1′) if [ "${host}" ]; then echo “Host ${host} is…

Post: Product to try: MySQL/MariaDB-Galera 0.8

limitations and come up with new features, but there is nothing to complain about it – a synchronous distributed transactional… much more complex than an average MySQL master-slave setup. Potential performance penalty:… slaves. With additional nodes, the response time will only increase. And in multi-…

Post: Percona XtraDB Cluster - installation and setup webinar follow up Q&A

… a high throughput despite the response time limitations. Even with parallel replication, the response time limits the number of transactions / second that you can do… or a slave on asynchronous replication, galera and built-in mysql replication are independent from each other. Q: I installed Percona…

Post: How Percona does a MySQL Performance Audit

… are a SaaS hosted application for data mining stock market transactions,” or whatever the case may be we’ve generally seen… queries, in total execution time. By the way, the slow query logs in the stock MySQL server are extremely limited, and for serious… information in the slow query log output. The stock MySQL server’s limitation of one-second granularity makes it hide problem queries…