May 24, 2012

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

to the secondary index definition can result in a lot of Random I/O. The purpose of MRR is to reducequery runs the optimizer would switch to using plan ‘a’, which does not involve MRR, and the query time for MySQL

Post: Troubleshooting MySQL Memory Usage

to guess and test, you can’t get information of how much memory connection uses and for which purposes it is allocated. ReducingIn Percona Server you can do better as you can query temporary tables too: mysqlin MySQL. Most suspected memory leaks end up being some run

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

How to get CPU consumption per query ? You can take a look at procfs for MySQL process: root@ubuntu:/var/log/mysqlto number of queries running will give average CPU usage per query. If you’re runningto reduce wait time and number of IOs per query as well as increase CPU time

Post: How To Test Your Upgrades - pt-upgrade

query-digest like the commands below # to limit the number of queries per fingerprint to test with. pt-upgrade –fingerprints –run-timein general how each fingerprint performs on the test servers. About 10% variation is tolerable and can be accounted for other MySQL

Post: Aligning IO on a hard disk RAID – the Benchmarks

to IO alignment yourself. In this case offset is correct, but file system is unaware how toto high concurrency response time in the first case is significantly better. It would be interesting however to run

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

Reducing the load by half through the load balancer did not restore proper response timequeries at 0-second threshold (all queries) and crunched it with mk-query-digest. Side note: bravo for Daniel figuring out how to make mk-queryto the MySQL source code are necessary. But in

Post: Distributed Set Processing with Shard-Query

… operations on reduced sets. Keep in mind, …how to distribute the computation of aggregation queries over time. I realised that I could apply these same mathematical concepts to distributed queries…-by reduction is run over the coordination…MySQL storage nodes are supported. Amdahl’s law applies to

Post: Reasons for MySQL Replication Lag

reduced performance causing replication to lag. Failed hard drive getting RAID inMySQL Restart MySQL Restarts may include recovery timeIn could be even system which queries mysql. I’ve seen monitoring updates which would add excessively expensive and frequent query

Post: MySQL EXPLAIN limits and errors.

to rebuild index by sort of key_cache as it can for MyISAM. EXPLAIN may take long time In MySQLin select in from clause EXPLAIN might never complete. Solution is to run EXPLAIN for statements in FROM clause separately before looking at main queryreduces number of passes MySQL had to

Post: MySQL Query Cache

to be cached. Query must be deterministic – Query might provide same result no matter how many times it is runreduce query_cache appropriately. Otherwise you might wish toto use query cache ? Third party application – You can’t change how it works with MySQL to add caching but you can enable query