May 24, 2012

Post: Heikki Tuuri Innodb answers - Part I

how many read-ahead requests can be queued at once. Q13: Is there any IO concurrency control – how many random and sequential read aheads canper flush. That means that under a heavy write load, a new flush and a checkpoint happens more than once per second

Post: Recovering Innodb table Corruption

rows affected (0.03 sec) mysql> insert into test2 select * from test; Query OK, 229376 rowscan find out how many rows do you need to skip exactly to recover as much data as possible. Row size can

Post: Just do the math!

MySQL may execute query above but lest focus on the most typical one – scan the table, when for each row insert (or update) rowcan also see how many rows query can process per second in total. Lets assume it is 100K rows per second … numbers you can feed into your model. Using the model we can get …

Post: Implementing efficient counters with MySQL

many thousands of updates per second with no problem (assuming log commit would not be bottleneck). Of course the fact you update short rowsinserts go to. The trick you can use here is standard “shadow table” trick – use two tables insert into one and process and truncate another. MySQL

Post: SHOW INNODB STATUS walk through

per second to start really worry for most CPUs. innodb_sync_spin_loops canMySQL thread id 9697561, query id 188161264 localhost root update insert intoinsert buffer. Next it shows how many inserts were done in insert buffer, how many recs were merged and how many

Post: Heikki Tuuri answers to Innodb questions, Part II

one read-ahead can happen at the same time. How many read-aheads canper second, then you write 1000 times per secondMySQL bugs opened about multi-core scalability (concurrent queries, autoincrement, concurrent insertsHow does this fit into

Post: Slow Query Log analyzes tools

per second puts more load on server than 10 seconds query running once per secondRows_sent: 0 Rows_examined: 0 INSERT IGNORE INTOINSERT/UPDATE ones. Final Note: You do not have to have patched MySQL

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

… anything near this many tables in the MySQL test suite. So…create 30,000 identical tables, insert a row into each of them and…25 per second. Of course, with the default timeout for a MySQL test (…. Since you could hear how much syncing to disk …than MySQL ever got. With HailDB you can do more than one