June 19, 2013

Comment: MySQL Partitioning - can save you or kill you

to a single table, where probably only recently read records will be cached, resulting in more disc reads. 2. If you need toqueries on any other column, these could easily be quicker on a partitioned table, as MysqlSelectsrows… for example, if you need to

Post: High-Performance Click Analysis with MySQL

columns to support these queries. But beware of denormalizing with character data; try to make your rowsto think about how to avoid enormous tables that are hard tosingle row created from many rows, and if the many rows don’t match completely, the singlequeries that read a lot of rowsMySQL

Post: How to recover deleted rows from an InnoDB Tablespace

how it could be possible to recover, on some specific cases, a single table from a full backup in order toto_date); Query OK, 3 rows affected (0.01 sec) Records: 3 Deleted: 0 Skipped: 0 Warnings: 0 mysql (employees) > select

Post: Multi Column indexes vs Index Merge

columns i1 and i2 independent in this case each selecting about 1% rows from this table which contains about 10M rows. mysqlquery scans a lot of rows and completed in about 290ms So we can see index merge indeed improves performance compared to single

Post: MySQL Indexing Best Practices: Webinar Questions Followup

SELECT * FROM TBL WHERE hash=crc32(‘string’) AND string=’string’ The other thing you need to consider is string comparison in MySQLto redesign schema and queries to make it work well. Q: how does a index be used having an index on one column

Post: How number of columns affects performance ?

single tinyint column which is almost shortest type possible (CHAR(0) could be taking less space), table with 1 tinyint columnto t99v1 table and repeated the query: mysql [localhost] {msandbox} (test) > select max(t1+0) from t99v1; +———–+ | max(t1+0) | +———–+ | 0 | +———–+ 1 row

Post: Multi-Column IN clause - Unexpected MySQL Issue

row in set (0.00 sec) As you can see just using multiple column IN makes MySQL toMySQL feature out there. For given application case we could simply rewrite query using more standard single column IN clause: mysql> explain SELECT

Post: Shard-Query turbo charges Infobright community edition (ICE)

MySQL data sets and queries. Another advantage is that it works with all MySQL storage engines. This set of benchmarks evaluates howto the staging tables, omitting the dimension columns from the projection, instead replacing them with the dimension keys: select

Post: Shard-Query adds parallelism to queries

MySQL never takes advantage of more than a single CPU when aggregating data and fetching rows from the buffer pool, with respect to a single query