June 18, 2013

Post: High-Performance Click Analysis with MySQL

which is really constructed behind the scenes from the name-value tables in a complex query with many joinsis clearly better for some workloads out-of-the-box than MySQL is, especially for more complex queries. Percona is not tied to MySQL

Post: Shard-Query EC2 images available

is 42GB, which ismysql> use ontime1; Database changed mysqlbetter than a row store for queries which access a significant amount of data. One big reason for this isuse are shown in the EC2 console. That the “private ip” field is selectedor two nodes. You should start two

Post: Faster MySQL failover with SELECT mirroring

which is just like normal master-slave replication except that you can fail over in both directions. Aside from MySQL Cluster, which isSELECT traffic, these same queries were responding nicely on the passive master, too. Is that all? “Buffer pool warmed up, performance is better

Post: Using Flexviews - part one, introduction to materialized views

MySQL even includes a SQL statement that makes this perfectly clear: CREATE TABLE .. AS SELECT (CTAS). The results of the SELECTor other conditions must be fully computed and stored in a temporary table before they can be accessed, which is very expensive. What is

Post: SHOW INNODB STATUS walk through

is much better to usemysql tables in use 1, locked 0 MySQL thread id 8079, query id 728899 localhost root Sending data selectis ALTER TABLE or similar statement, or if LOCK TABLES was used. In addition to Innodb specific information, there is generic statement information which is

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

MySQL always uses Nested Loop Join to join two or more tables. What this means is that, select rows from first table participating in the joinsJoin as compared to Nested Loop Join, but for now it looks like Nested Loop Join is a much better general purpose join

Comment: Database problems in MySQL/PHP Applications

which allows to do > $dbcon->query(ā€œSelect email from user where name=%sā€,$name) – > wrapper will detect query isusing > Join. This is typical error. On other hand in MySQL you might be > better of using

Post: Joining on range? Wrong!

joins only. When you use a range condition on the first (or the only) table, it works as expected: EXPLAIN SELECTUsing where; Using index In this case MySQL does not print ref at all, because there is no join, however you can notice key_len isbetter

Post: MySQL extensions for hosting

or scan the slow log live, but that is a bit ugly solution. That is where this patch can be very useful. With simple MySQLSELECT query transformations, joins and better filtering for the statistics Also combining these new commands with our msl patch, which

Comment: Innodb Performance Optimization Basics

or recovers in some other way which is slow. This can seriously impair your performance! My only wishes for mysqlSelect_full_join and 0 Sort_merge_passes though finally. What is most confidence inspiring is