
We've noticed contention in binary log syncing to disk, so I got back to micro-benchmarking edge cases...

MySQL@Facebook Who knew InnoDB could spend so much time checking for deadlocks?

MySQL@Facebook
MySQL 5.1.41 has been released with the InnoDB 1.0.5 plugin. This is a great release. Read about it at http://dev.mysql.com/doc/refman/5.1/en/n ews-5-1-41.html
dev.mysql.com
:: C MySQL Change History :: C.1 Changes in Release 5.1.x (Production) :: C.1.1 Changes in MySQL 5.1.41 (05 November 2009)

I pushed more patches to the Facebook patch for MySQL. Expect more patches as several people are on the team (Domas committed a change today). We will soon be publishing patches for MySQL 5.1. The patches include: Protect InnoDB LRU during full table scan...

The 10 largest tables in one production database use 17.8G with InnoDB, 11.1G with MyISAM and 8.6G with packed MyISAM. From tests done by Ryan show that InnoDB compression reduces our database to 59% of the original size...

MySQL@Facebook When will Paul talk about Flash Cache and Flash AWEsome?

I've completed an initial round of testing InnoDB with data compression and the results are extremely promising. The testing was performed by setting up two shadows of a production database...

At the end of this note I describe how InnoDB can be much faster (2.5X) for high-concurrency workloads. However, what we really did is improve the code to not get 2.5X slower. InnoDB uses innodb_thread_concurrency to limit the number of threads that run concurrently...

InnoDB uses background threads to handle readahead (prefetch) requests. Requests are generated when it detects sequential or random access to most blocks in an extent. This is described in the 5.0 MySQL manual with new behavior in the plugin...

We have servers that run with innodb_log_file_size=256M and some of these servers do a lot of disk writes per second...

I am Domas Mituzas, and I have just joined Facebook MySQL team. I've been working at MySQL Support before, as well as did Wikipedia data and performance engineering on my free time - and I've blogged about that a bit...

InnoDB uses a 16kb page by default. I want to know whether performance improves with an 8kb database page for my workload. Two servers were setup to run a mirror of the production database workload. One used 8kb InnoDB pages and the other used 16kb...

I was debugging a server that had too many concurrent queries. From SHOW INNODB STATUS output, there were many long running transactions with uncommitted work and there were many more transactions blocked on InnoDB locks...

Hello. I'm Ryan Mack, a new member of the Facebook MySQL team. My first order of business is evaluating MySQL 5.1 and the new InnoDB plugin. So far things look very promising, but I came across one issue worth sharing...









