June 20, 2013

Post: read_buffer_size can break your replication

… going to talk about read_buffer_size and how this …to load the 4 million rows with LOAD DATA INFILE: MasterA (test) > LOAD DATA INFILE ‘/tmp/data’ INTO TABLE t; Queryto check the binary logs of both masters. MasterA: masterA> mysqlbinlog data/mysql-bin.000004 | grep block_len #Begin_load_query

Post: Distributed Set Processing with Shard-Query

how 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 toCHECK * on the base table

Post: Is MySQL 5.6 slower than MySQL 5.5?

to be considered for the query the more time the query optimization is likely to take. I also would expect newer code tomysql-socket=/tmp/mysql_sandbox5610.sock –mysql-user=msandbox_rw –mysql-password=msandbox –oltp-table-size

Post: InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

Checks | 24.224336624145508 | +—–+————————————————————————–+——————–+ OK, now I’m starting tomysql: SET GLOBAL innodb_ft_server_stopword_table=’test/innodb_ft_list2′; Query OK, 0 rows affected (0.00 sec) mysql

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

query, see how many pages were read from disk versus how many page requests their were: mysqltables | 0.000015 | 0.000016 | 0.000000 | 0.000000 | 0 | 0 | 0 | 0 | 0 | 0 | | 3 | checking

Post: Heikki Tuuri answers to Innodb questions, Part II

size Q36: There have been several MySQL bugs opened about multi-core scalability (concurrent queriestable where id=5 show innodb status: Hash table sizecheck with Alexander or check myself to

Post: Investigating MySQL Replication Latency in Percona XtraDB Cluster

to pretty significant load. sysbench –test=oltp –mysql-user=root –mysql-password=”" –oltp-table-sizeto DPE1 is blocked for some time. To check this idea I decided to use the sysbench script with very simple point update queries to

Post: Recovering Innodb table Corruption

to CHECK your MyISAM table you use for recovery after MySQL crashes to make sure indexes are not corrupted. So we looked at how to

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

to find out how to make InnoDB FTS blazingly-fast, but simply to get a sense of how it works compared tomysql> delete from dir_test_innodb LIMIT 200000; Query OK, 200000 rows affected (8.65 sec) mysql> optimize table dir_test_innodb; +———————-+———-+———-+———-+ | Table

Post: Find unused indexes

MySQL we should try another approach. Percona Toolkit has a tool to check the usage of our index from the slow querysize. Conclusion We’ve learnt how to