June 19, 2013

Post: MySQL Query Patterns, Optimized - Webinar questions followup

a presentation on “MySQL Query Patterns, Optimized” for Percona MySQL Webinars.  If you missed it, you can still register to view the recording and my slides. Thanks toto the query where you were trying to determine the last episode of each TV show. Couldn’t you have used a SUBQUERY to fetch

Post: Using GROUP BY WITH ROLLUP for Reporting Performance Optimization

query to illustrate some search is required, so count(*) can’t be optimized away for MyISAM Tables. To show percents for theMySQL for reporting quite expectedly starts to become the bottleneck. We use a lot of other black magic to

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

the purpose of this benchmark, I have used TPC-H Query #10 and ran it on TPC-H dataset (InnoDB tables) with athe start of the post that traditional index lookup (for non-index-only columns) involves, reading an index record, and then using the

Post: Improved InnoDB fast index creation

To illustrate this, I have performed a number of simple benchmarks. Let’s start with a table containing 4 million rows and one secondary key: mysqlto the default method, because it does not have to do random disk seeks to fetch secondary index pages to the buffer pool. A benchmark is worth a

Post: Innodb Table Locks

start with some examples. First lets run SELECT Query: —TRANSACTION 12303, ACTIVE 26 sec mysql tables in use 2, locked 0 MySQL…mode IS RECORDthe entries in this index rather than primary key. Lets now see about writes: —TRANSACTION 12304, ACTIVE 3 sec fetching rows mysqla good practice not to

Post: Heikki Tuuri Innodb answers - Part I

the 768 byte local storage in the record. In that source code tree, InnoDB only needs to store locally athe MySQL binlog write and the InnoDB log flush with a mutex in 5.1, to implement XA, and switching off the

Post: Analyzing Slow Query Table in MySQL 5.6

query information to the log file, it outputs the query time and lock time as floating-point numerics to microsecond scale: sql/log.cc, MYSQL_QUERYthe times recorded in slow query log tables are rounded down to the nearest whole second, meaning any query

Post: SHOW INNODB STATUS walk through

to use this info to improve MySQL Performance. To start with basics SHOW INNODB STATUS is command which prints out aMySQL thread id 30899, query id 100627 localhost root Updating update iz set pad=’a‘ where i=1 *** (2) HOLDS THE LOCK(S): RECORD

Post: Recovering Innodb table Corruption

the data portion of pages so once you started Innodb with innodb_force_recovery=1 you can do the following: mysqlto MySQL server during query mysql> insert ignore into test2 select * from test where id>300; Query OK, 573140 rows affected (7.79 sec) Records