June 19, 2013

Post: Top 5 Wishes for MySQL

from MySQL to do so. What is really bad is Parallel queryMySQL has very good stability track record, with exception of MySQL 5.0 it was typically safe tothe work is going on and it just takes time to get them all fixed. 5. Do not forget about the roots. MySQL

Post: InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

the words “James” and “Peterson”, and we should expect the record from Arizona to be towards the top of the list. With 5.5, this is exactly what happens: mysql

Post: How Percona does a MySQL Performance Audit

the query, the server could have died. The ORM should just be running the query, and if the query fails, then you know from the error code that thethe mysql.* tables, running mk-duplicate-key-checker to find redundant indexes, and so on. As with settings and status, these set the

Post: How to find MySQL queries worth optimizing ?

query examining same amount of rows as they end up sending. In this case if I index the table I get the following record in the slow query…returned up to the top level MySQL part for processing are counted the Rows_examined…from sbtest a,sbtest b where a.id=5 and b.id=a.k; mysql> explain select * from

Post: High-Performance Click Analysis with MySQL

the chance to parallelize.  As you know, MySQL doesn’t do intra-query parallelization, so ETL jobs written to rely on SQL tend to getthe clicks column record the total, and the blue_clicks column record only blue clicks; to find out non-blue clicks you subtract one from the

Post: Shard-Query adds parallelism to queries

the improved MySQL 5.5 partitioning options which work directly on columns without the need to use TO_DAYS. To accommodate my partitioning schema I modified the queries to use therecords. This table is partitioned by month which means that MySQL can use partition pruning to reduce the

Post: Faster MySQL failover with SELECT mirroring

from MySQL Cluster, which is more special-purpose, this is probably the best general-purpose way to getquery against these three sets of stats to find the top tables on the active server and left-join those against the tables on the

Post: MySQL Slow query log in the table

queries coming to the top of the list rather than in the end. If you want to get new queries in the end you can do SELECT * FROM (SELECT * FROMto sort records by physical position quickly without need to have indexes would be quite handy I also should tell log table implementation in MySQL

Post: Read/Write Splitting with PHP Webinar Questions Followup

to get a recording once it is over? A: Yes, we will email a link to all webinar attendees with a recording of thethe MySQL database for persistence, but when we measured query load with pt-query-digest, we found that 30% of the

Post: ORDER BY ... LIMIT Performance Optimization

from the index can be used to satisfy order by, index however will not be helpful to check c=5 (unless it is index covered querytable: mysql> explain select test.i from test, test t where test.i=5 and test.k=t.k order by t.k limit 5