… use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and… you did not attend my talk – you are welcome to join the webinar. Follow @VadimTk !function(d,s,id){var js…
Post: Testing STEC SSD MACH16 200GB SLC
… use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and… you did not attend my talk – you are welcome to join the webinar. Disclaimer: This benchmark is done as part of…
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
… are the join optimizations when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer… are the join optimizations when the workload is IO bound. For the purpose of benchmarking IO bound workload, the InnoDB buffer pool… 2.2G Innodb_data_reads 329115 355323 143808 335526 16164 15506 Innodb_pages_read 329115 355323 143808 358308 144798 144881 Innodb_rows_read…
Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables
… WITH READ LOCK is waiting for that very nasty “full join” select to complete. What is worse as the statement started… gridlock one way or another. If you’re just using Innodb tables and you’re not actively changing users, stored procedures…
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
… 20920 23734 Innodb_buffer_pool_read_requests 1361851 1264739 1235472 1263290 1235781 Innodb_buffer_pool_reads 120548 102948 76882 102672 76832 Innodb_data….89G 1.53G Innodb_data_reads 120552 123872 100551 103011 77213 Innodb_pages_read 120548 123868 100551 123592 100566 Innodb_rows_read 799239… lookups as well. But this works only with joins and specifically with Block Access Join Algorithms. So I am not going to…
Post: MariaDB 5.3 is released as GA!
… log enabled Faster queries through speedier joins, faster subqueries, and elimination of useless tables in joins Thread pooling and a segmented key…, better diagnostics, improvements to partitioning, and the addition of multiple InnoDB buffer pools. Best of all, MariaDB 5.5 might be…
Post: How well does your table fits in innodb buffer pool ?
…) bp JOIN innodb_sys_indexes ON id = index_id JOIN innodb_sys_tables ON table_id = innodb_sys_tables.id JOIN innodb_index_stats ON innodb_index_stats.table_name = innodb_sys_tables.name AND innodb…
Post: SHOW INNODB STATUS walk through
… thread is not runniing inside innodb kernel status could be “waiting in InnoDB queue” or “sleeping before joining InnoDB queue”. Latest one is quite interesting – to avoid too many threads competing to enter innodb queue…
Post: How to recover deleted rows from an InnoDB Tablespace
…) > select i.INDEX_ID, i.NAME FROM INNODB_SYS_INDEXES as i INNER JOIN INNODB_SYS_TABLES as t USING(TABLE_ID) WHERE t.NAME=’salaries’; +———-+———+ | INDEX_ID | NAME | +———-+———+ | 26 | PRIMARY | | 27 | emp_no | +———-+———+ B) InnoDB…
Post: Using CHAR keys for joins, how much is the overhead ?
….1.18 using MyISAM and Innodb tables. This time unlike other benchmarks I decided to do Join not on primary key and… as default ? Joining on Char columns completes in 4.5 seconds on Innodb which is about 50% slower compared to Joining on Int….5 seconds which is just 20% slower than integer based join for Innodb. Finally I decided to check if using longer strings…

