June 19, 2013

Post: High-Performance Click Analysis with MySQL

large amounts of space.  Choose primary keys very carefully, especially with InnoDB tables — don’t use GUIDs.  Which brings me toin MySQL 5.0 and earlier, doing the work on a slave, then piping the results back up to the master with LOAD DATA

Post: MySQL Query Cache

of queries in cache and memory used can’t grow forever even if your have very large amount of different queries being run. Of course inhow it works with MySQL to add caching but you can enable query cache so it works faster. Low load

Post: Using any general purpose computer as a special purpose SIMD computer

large amount of input. Often times, the same function must be run on many pieces ofMySQL client. This will be a linear operation because Shard-Query has no idea how to add parallelism in this case. It is data

Post: Optimizing InnoDB for creating 30,000 tables (and nothing else)

… huge improvement. So how could I possibly get this test to run (even with –big-test option to mysql-test-run) in reasonable time? Well… clear that loading large amounts of DDL could be a lot faster than it is currently (although loading the data into tables is still going to take…

Post: Shard-Query EC2 images available

amount of data. One big reason for this is the excellent compression that RLE techniques provide. I have not loadedlarge datasets effective compression results in the need for fewer nodes in order to keep data entirely in memory. This frees disk to

Post: Quickly finding unused indexes (and estimating their size)

amount of disk space for it to be worth our while? We need some more information to answer this question, but fortunately inhow big each index is if we dropped it (not big in this case with test data): mysql

Post: MySQL 4 to MySQL 5 Upgrade performance regressions

to use. How to fix the problem ? Assuming getting back to MySQL 4.1 is not the option you can do one of 3 things toof course to work on the application – in large amount of cases the problem happens in case there are away to many updates outside of transactions in

Post: How expensive is MySQL Replication for the Master

… generally thought about MySQL replication as being quite low overhead on Master, depending on number of Slaves. What kind of load extra Slave causes… possible to get some auto detection in place timing how long it really takes all threads to send their data to the slave. If you have large amount of

Post: SHOW INNODB STATUS walk through

how to use this info to improve MySQL Performance. To start with basics SHOW INNODB STATUS is command which prints out a lot oflarge amount of spin waits and spin rounds significant CPU resources may be wasted. It should come to hundreds of thousands spin rounds per second to

Post: Investigating MySQL Replication Latency in Percona XtraDB Cluster

in similar amount of cases but delay is higher in this case both in average and the Maximum one. This tells me from datato large transactions you can get in a lot of trouble with major stalls both in terms of data propagation and in terms of