May 24, 2012

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

0.02s. But the query times for MariaDB 5.5 are greater than both MySQL 5.5 and MySQL 5.6 IO bound workload Now let’s see howin the buffer the more sequential the access pattern will be. There is one MRR related variable introduced in MySQL 5.6 and MariaDB 5.5

Post: Troubleshooting MySQL Memory Usage

0.00 sec) Innodb Memory Usage Finally it is often helpful to check how much memory Innodb has allocated. In fact this is often onein MySQL. Most suspected memory leaks end up being some run

Post: Upgrading MySQL

one. MySQL 5.0 to 5.1 upgrade is a lot safer upgrade path than 4.1 to 5.1 just because so much morein MySQL 4.1 or changing JOIN evaluation in 5.0 (which could both cause different result set or make query not runnable in MySQL 5.0) In

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

how many queries needed no io, needed 1 IO which was not queued (less than 10 ms) or needed more thanhow much does it cost to run a query. With Cloud Computing being hot a lot of Directors would like to know the costs in

Post: Flexviews - part 3 - improving query performance using materialized views

to storing the results of a query inin set (43 min 10.11 sec) As an added benefit, if you build more than one complete refresh view from an incrementally refreshable one

Post: The story of one MySQL Upgrade

to be upgraded. It is a shared database used by tons of applications written by many people over more than 5in the tables. It turned out one of the float columns stored “-0in MySQL 5.0 but it was displayed as “0” when data loaded to Percona Server 5

Post: High-Performance Click Analysis with MySQL

one of the most common questions we hear is how to build high-performance systems toqueries do you have to run?” and they say “we can’t decide, so we want toMySQL 5.1′s row-based replication, or in MySQL 5.0 and earlier, doing the work on a slave, then piping the results back up to

Post: Shard-Query EC2 images available

more than one node. This would not be the case into examine the differences in size. This will give us some interesting information about how Shard-Query will perform on each database. To0.637 ms … Note: There is no need to put that hosts file on your other nodes unless you want to run

Post: Is your server's performance about to degrade?

queries are running faster than one millisecond; some in the 50 to 100 microsecond range. At such speeds, howquery cache) are executing in no more than 12 microseconds, worst-case. So the contention that’s blocking these queriesto the MySQL source code are necessary. But in

Post: MySQL VIEW as performance troublemaker

in MySQL 5.0 and quite frequently VIEWs are used to help in writing the queriesto keep queries simple without really thinking how it affects server performance. Even worse than