May 25, 2012

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

… preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking… Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take a look briefly at what… WHERE condition defined as: l_partkey = x and l_quantity >= 1 and l_quantity = 1 and l_quantity

Comment: How to recover a single InnoDB table from a Full Backup

InnoDB: Import: The extended import of data is being started. InnoDB: Import: 9 indexes have been detected. InnoDB: Progress in %: 1 2 3 4 5InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB

Post: What is stored InnoDB buffer pool

0 | 0 | 7 | 0 | 0 | 0 | 0 | 2 | 6 | unknown | | | | | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 3 | 5 | unknown | | | | | 2 | 0 | 3 | 0 | 0 | 0 | 0 | 4 | 6 | unknown | | | | | 3 | 0 | 2 | 0 | 0 | 0 | 0 | 5 | 3 | inode | | | | | 4 | 0 | 4 | 0 | 0 | 0 | 0InnoDB plugin MySQL 5.1

Post: Find where your data is replicated, win a Percona Live ticket

… first — have you ever wondered what servers are in your MySQL replication hierarchy? We have, too. As consultants, a lot of… InnoDB version 1.0.16-12.8 +- 10.124.62.77 Version 5.1.57-rel12.8-log Server ID 6277 Uptime 12+04:00:240 seconds behind, running, no errors Slave mode STRICT Auto-increment increment 1, offset 1 InnoDB version 1.0.6-unknown +- [redacted].compute-1.amazonaws.com Version 5.1

Post: Identifying the load with the help of pt-query-digest and Percona Server

…as in MySQL. This…0 # Rows affecte 1.34k 0 65 0.07 0 1.35 0 # Rows read 105.76k 0 1000 5.39 9.83 32.69 024.84 # Rows examine 8 45.05k 0 1.05k 309.59 1012.63 299.07 124.25 # Rows affecte 0 0 0 0 0 0 0 01 more # Hosts # InnoDB trxID 86B40F (1/0%), 86B429 (1/0%), 86B434 (1/0%)… 146 more # Last errno 0

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

0 0 0 0 0 0 0 0 # rec lock wai 0 0 0 0 0 0 0 0 # String: # Databases # Hosts localhost # InnoDB trxID 3BBF3B55 (1/0%), 3BBF3B5A (1/0%)… 1753695 more # Last errno 0

Post: SHOW INNODB STATUS walk through

…internal Innodb performance counters, statistics, information about transaction processing and all kinds of other things. In MySQL 5 number of Innodb0 42313620, ACTIVE 24 sec, process no 10099, OS thread id 4078512 starting index read, thread declared inside InnoDB 500 mysql tables in use 1

Post: Scaling problems still exist in MySQL 5.5 and Percona Server 5.5

MySQL 5.5 and Percona Server 5.5 do…: SELECT * FROM table WHERE deleted = 0 AND group_id IN (62715996, 62716592, 62717660…5.1.56-12.7 and Percona Server 5.5.11-20.2 with former being configured with innodb5.1 and around 6 for Percona Server 5.5 which is way too little for what you would expect from 24

Post: How much overhead is caused by on disk temporary tables

…MyISAM storage engine. The benchmarks are done with MySQL 5.0.45 on 32bit Fedora Core 6 on Pentium… not forget about it especially if running only Innodb tables so you may think there is no…0 0 3 116 56248 9104 549212 0 0 2 2023 1518 498 5 2 10 83 0 1 3 116 56316 9104 549228 0 0 0 2121 1539 497 0 1 24

Post: Percona Server 5.1.58-12.9

… upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24. A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1.24. If… warnings will be printed for the deprecated options (innodb_buffer_pool_shm_key and innodb_buffer_pool_shm_checksum) if used. Instructions…