June 20, 2013

Post: Benchmarking Percona Server TokuDB vs InnoDB

looking at the graph, please do not jump to conclusions, as thethe transactionmysql #for SSD innodb_flush_neighbor_pages = none innodb_adaptive_flushing_method = keep_average innodb_file_per

Post: Investigating MySQL Replication Latency in Percona XtraDB Cluster

looking for the best performance possible. So far so good. We can make cluster to handle significant load with small transactionsto see how the latency is impacted: mysql> update sbtest2 set k=k+1; Query OK, 1000000 rows affected (1 min 14.12 sec

Post: What MySQL buffer cache hit rate should you target

per second. And at the same time you have some performance critical transactionto look at the number of misses – number of IOs which MySQL needs to do. You better to look at global and local (per

Post: SHOW INNODB STATUS walk through

MySQL thread id 30898, query id 100626 localhost root Updating update iz set pad=’a’ where i=2 *** (1) WAITING FOR THIS LOCK TOtransactions is displayed, while locks rows could be locked by one of previous statements. For complex deadlock investigations you might need to look at the

Post: Mystery Performance Variance with MySQL Restarts

mysql_sandbox5610.sock with 1 threads transactions: 99210 (330.70 per sec.) transactions: 99733 (332.44 per sec.) transactions: 99766 (332.55 per sec.) transactions: 99838 (332.79 per sec.) transactions: 100035 (333.45 per sec

Post: Percona XtraDB Cluster: Multi-node writing and Unexpected deadlocks

the course of the transaction.  If a given statement in the transaction needs a lock, it will wait for that lock before proceeding (this is wheretransactions and attempt to modify the same row: node1 mysql> set autocommit=off; Query OK, 0 rows affected (0.00 sec) node1 mysql

Post: Reasons for run-away main Innodb Tablespace

where Trending can help, for example MySQL CACTI Templates will have the graphs you need. If you’re lookingper transactionto be accommodated in the database. It is not limited to undo slots. When we’re speaking about Long Transactions the

Post: Introducing tpce-like workload for MySQL

looking into different benchmarks, and one of them is TPCE. Yasufumi made some efforts to make TPCE working with MySQLwhere you can see count of successful TR (TradeResult) transactions, and the summary result in TpsE (transactions per

Post: MySQL extensions for hosting

for the hardware to process from even small tables. Therefore often the resulting database load may not be directly related to thewhere this patch can be very useful. With simple MySQL SHOW command it gives you the basic statistics on thetransactions: 0 Rollback_transactions: 0 mysqlsec) mysql

Post: How to calculate a good InnoDB log file size

for choosing a configuration setting, you should looksec) Notice the log sequence number. That’s the total number of bytes written to the transactionmysql> select (3838334638 – 3836410803) / 1024 / 1024 as MB_per_min; +————+ | MB_per