June 18, 2013

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

and memory consuming, so ideally you would want to download the “slow query log” to another machine andTables” section lists the queries that you can use to gather more data about the underlying tables involved and the query execution plan used by MySQL

Post: MySQL Indexing Best Practices: Webinar Questions Followup

…lot of performance gains before I move to such unusual setup. Q: Table1 has… column and using order by on another column. do i need to add the index on columntable or filesort for group by by this column. This works because by scanning data in index order MySQL gets data in already sorted order and

Post: Troubleshooting MySQL Memory Usage

to see MySQL memory consumption plotted. I use “VSZ” columns from “ps” output on Linux. It helps me totable cache, especially if you’re using large blobs. It is easy to check though. Run “FLUSH TABLESand

Post: A recovery trivia or how to recover from a lost ibdata1 file

to recover data. Basically, while doing a transfer from one SAN to another, something went wrong and they lost the ibdata1 file, where all the tablemoving the datafile in place” cp /mnt/tables/$CURRENT_TABLENAME.ibd /var/lib/mysql/recover/ chown mysql.mysql /var/lib/mysql

Post: Why you don't want to shard.

tables, and move them onto their own MySQL server.  Partition-by-function keeps the architecture still simple, andcolumn on a table and try and divide up your data based on it.  You can choose any column to hash on, you just need to

Post: High-Performance Click Analysis with MySQL

data you’ll need in those aggregate tables, and include columns to support these queries. But beware of denormalizing with character data; try toto-scale component in your system — don’t waste resources. Another benefit of this is the chance to parallelize.  As you know, MySQL

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

… InnoDB table: SELECT non_key_column FROM tbl WHERE key_column=… Now let’s move on to the benchmarks, to see the ….89G 1.53G Innodb_data_reads 120552 123872 100551…to MySQL 5.5 MRR clearly changes the access pattern to sequential, and hence InnoDB is able to do many read_aheads. Another thing to

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

to actually matter at table creation time. Once I’ve got a table with an explicit FTS_DOC_ID column, however, MySQLand then running OPTIMIZE TABLE, and that we might have to run OPTIMIZE TABLE multiple times if we’ve had a lot of changes to the table

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

table fits in memory. You can read more about the hash join algorithm here. Now let’s move on to the benchmarks, toto 6M and the read_rnd_buffer_size is set to 6M. MariaDB 5.5 is close, yet slower by ~10s. Anotherto MySQL 5.6. Next interesting thing are the last two columns of the table above and

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

… comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one… both MySQL 5.6 and MariaDB 5.5 Now let’s take a look briefly at what this enhancement actually is, and what…`,`l_shipmode`,`l_shipinstruct`) and the WHERE condition defined as: l_partkey = x and l_quantity >= 1 and l_quantity = 1 and l_quantity