May 24, 2012

Post: Statement based replication with Stored Functions, Triggers and Events

Statement based replication writes the queries that modify data in the Binary Log to replicate them on the slave or to use it as a PITR recovery. Here we will see what is the behavior of the MySQL when it needs to

Post: Shard-Query EC2 images available

to use on-disk temporary storage for hash joins and other background operations. This will have a direct impact in our queryquery script will run one more more semicolon terminated SQL statements. The queries for the benchmark are in ~ec2-user/shard-query/queries

Post: Distributed Set Processing with Shard-Query

statements breaks down into a relational algebra equation. Inhow to distribute the computation of aggregation queries over time. I realised that I could apply these same mathematical concepts to distributed queriesMySQL storage nodes are supported. Amdahl’s law applies to

Post: Using Multiple Key Caches for MyISAM Scalability

In MySQL 4.1 the lock is held only when key block (1KB to 4KB) is being copied from Key Cache toquery which will return statements to initialize key buffers according to table sizes and activity (in this case taken with 50-50 weight though you may use

Post: Faster MySQL failover with SELECT mirroring

queries were responding nicely on the passive master, too. Is that all? “Buffer pool warmed up, performance is better, casestatementsto use some technique to mirror the read-only workload to the passive server. It doesn’t have to be the tools I used

Post: Should you move from MyISAM to Innodb ?

in the end for most users – you do not get to deal with recovering tables on the crash or partially executed statementsqueries. In case MyISAM was chosen not just happened to be it is important to build the good argument to

Post: Analyzing air traffic performance with InfoBright and MonetDB

to execute and 29.9 sec for MonetDB, but it’s almost single case…` varchar(50) DEFAULT …using included sqlline utility, and I did not understand how to do that, so I generated big SQL file which contained load statementsquery in InfoBright. MySQL is really stupid here, and EXPLAIN for this query

Post: New SpecJAppServer results at MySQL and Sun.

statements generally should have helped this benchmark because it has a lot of same queries an Prepared Statementsused so I’m curious how much speed benefit did it really provide in this case

Post: Recovering Innodb table Corruption

MySQL. In this case we can expect this is the row between 200 and 300 and we can do bunch of similar statements tohow to get your data back from simple Innodb Table Corruption. In more complex cases you may need to use higher innodb_force_recovery modes to

Post: ORDER BY ... LIMIT Performance Optimization

In some cases even if it is possible to use index to do ORDER BY with JOIN MySQL still will not be able to useto use appropriate index. One more note about ORDER BY … LIMIT is – it provides scary explain statements and may end up in slow query