Original, and very large, image:
krow.net/images/drizzle-mem-gear-developers.jpg

A Launchpad project, mysqlatfacebook, has been created to publish patches for MySQL from Facebook. The patches are based on MySQL 5.0.84. A few changes have been published and more are to come. The focus for many of our early changes is to add performance counters to InnoDB. We want to make InnoDB faster and these changes make it easier to understand where time is spent today. Some of the initial changes are derived from the Google patch. Changes include:

• A fix for bug 46459 to improve performance for concurrent autocommit statements.
• Options to disable readahead (prefetch) in InnoDB
• Options for InnoDB IO performance including:
  • innodb_io_capacity - sets the IO …

The program is very rich. There will be several tracks in the main event and in the associated conferences. If …

Dear Community,

The release 0.9 of the opensource backup tool for InnoDB and XtraDB is available for download.

Changelog:

• tar4ibd could not treat over 8GB file, now max 64GB
• prepare-speed-hack is added

Fixed bugs:

• Bug #386179: "InnoDB: Error: space id in fsp header 143088, but in the page header 0"
• Bug #394374: "Can't compile with MySQL 5.1"
• Bug #394781: "xtrabackup requires write permissions on original ibdata1"
• …

There is a detailed announcement that warns against using these binaries in production, but encourages everyone to test them. A companion tutorial explains how to use the snapshots to test the InnoDB plugin, which was released recently, and it is included in the latest MySQL …

I arrived yesterday in St. Augustin, near Bonn in Germany. After a good day of hitchhiking (weather is beautiful here) I stayed with my Pakistani Couchsurfing host and we had an extremely interesting evening talking about the gigantic cultural differences between western civilization and Pakistani civilization. It beats staying in a hotel by about a million points

This morning I headed to the FrOScon HQ at the fachhochschule to help out with whatever was needed. Turns out that was a bit premature (misunderstanding on my part), so I have had some time to catch up on mail and give some more attention to my talk on Saturday. I’ll be helping out throughout the and the whole day tomorrow with things though.

I’ll be talking about MySQL MMM, a project that I have invested …

Just want to point you at a new bug-fix release of XAMPP for Mac OS X. This version fixes control panel issues with Mac PowerPC computers.

Get the new version at http://www.apachefriends.org/en/xampp-macosx.html

In his blog Does the GPL Matter? In a Word, Yes, Stephen O'Grady makes the significant point that the dual-licensing model has a major drawback:

Sun/MySQL can only include patches and contributions if they fully own the copyright to those changes.

This gives forks like Drizzle, OurDelta, Percona and MariaDB a major advantage over the Sun version: they can include the best patches from all over. And it is clear that the momentum is building.

In a follow-up blog, Stephen asks: "what would the implications be if MySQL, of all projects, were forced to abandon the dual-licensing model it had long championed?"

Thinking about this, there is something that really bothers me:
…

One of the things that repeatedly seem to puzzle users about the DRBD is the question of whether to use internal or external metadata. Remember, DRBD sets aside a small area on a local disk (on every cluster node) where it keeps the Activity Log, the quick-sync bitmap, data generation UUIDs, and a few other bits and pieces for local housekeeping.

The specific aspect that is to be discussed here is the Activity Log. Without going into too much detail, let’s be satisfied with the factoid that DRBD …

As a consultant I would be rich if I made money every time when asking “Have you checked the MySQL error log?”

Today’s special found in a 13GB MySQL server error log.

090819 22:49:37InnoDB: Warning: difficult to find free blocks from
InnoDB: the buffer pool (1101071 search iterations)! Consider
InnoDB: increasing the buffer pool size.
InnoDB: It is also possible that in your Unix version
InnoDB: fsync is very slow, or completely frozen inside
InnoDB: the OS kernel. Then upgrading to a newer version
InnoDB: of your operating system may help. Look at the
InnoDB: number of fsyncs in diagnostic info below.
InnoDB: Pending flushes (fsync) log: 0; buffer pool: 0
InnoDB: 167 OS file reads, 1 OS file writes, 1 OS fsyncs
InnoDB: Starting InnoDB Monitor to print further
InnoDB: diagnostics to the standard output.
090819 22:49:37InnoDB: Warning: difficult to find free blocks from
InnoDB: the buffer pool (1101051 search iterations)! Consider
InnoDB: increasing …