Here is a quick comparison of the new InnoDB plugin performance between different compression, row formats that is introduced recently.

The table is a pretty simple one:

CREATE TABLE `sbtest` (
  `id` int(10) unsigned NOT NULL,
  `k` int(10) unsigned NOT NULL DEFAULT '0',
  `c` char(120) NOT NULL DEFAULT '',
  `pad` char(60) NOT NULL DEFAULT '',
  PRIMARY KEY (`id`),
  KEY `k` (`k`)
) ENGINE=InnoDB ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8;

The table is populated with 10M rows with average row length being 224 bytes. The tests are performed for Compact, Dynamic and Compressed (8K and 4K)  row formats using MySQL-5.1.24 with InnoDB plugin-1.0.0-5.1 on Dell PE2950  1x Xeon quad core …

KAs during last year's MySQL Conference, we invited Julian Cash to take pictures of some attendees. I managed to get my picture taken in last second - the hotel staff was already complaining that they need to redecorate the room for the next event...

The results of this foto session are now on Julian's photo stream on Flickr - I am really impressed by the results! This puts a whole new meaning to the term "MySQL Luminaries"

Kaj's pictures are pretty funny, too - is this an interpretation of "MySQL Community" vs. "MySQL Enterprise"?

…

Earlier, I noted that Julian Cash was to do some “light painting” at the MySQL Users Conference. And boy, did he do it!

He had a normal conference room, the Bayshore at the MySQL Conference, made a bit darker. Not pitch dark, but let’s say too dark to read. Then, he had us sit down on a chair in front of a neutral background, and took the pics with his camera mounted on a tripod. A picture took perhaps 30 to 60 seconds. After opening the shutter, the object was supposed to sit still. Julian then lit up our faces, in my case with blue and red light sources (”mini-torches”) which he moved top-down. Then, he sprinkled in some additional stray light in various colours.

I had asked for a picture …

I read very nice post by Matt today and it has many good insights though I can't say I agree on all points.
First there is a lot of people out where which put it as disk is everything. Remember Paul Tuckfield saying "You should ask how many disks they have instead of how many systems they have" on MySQL UC2008 Scalability Panel ? Indeed disks MAY be the most important part in your system performance or it may not be. Different people get to deal with different systems and so acquire different feeling about percentage of cases when disk would be the problem.

However it is not always the case. There are whole classes of systems where Disk performance is not that important - consider for example systems where most of the database fits in memory. These days we can get 64G of memory for pretty commodity prices and this allows you to get a lot of data in. Many …

When I was on the MySQL Documentation team one thing started to become apparent to me: the MySQL Reference Manual was exactly what it claimed to be: a document better suited to referencing than teaching new users. I make very good use of it because I know MySQL, I know what it can do, and all I want is the right syntax for what I am trying to use it for.

I saw a need for a User Guide, something well suited to new users who were not experienced with MySQL and potentially with DBMSes in general. As a side project I started working on a chapter of what could eventually be a MySQL produced user guide, lacking the depth of the reference manual but more suitable for newer users. This first chapter was on Indexing and while I think it showed promise, I left MySQL AB shortly after completing it.

Fast forward to today, where I see a blog post by Colin Charles …

Who’s Barton George?

Barton is a colleague from Sun, who “looks after Sun’s relationships with the various GNU/Linux communities as well as our relationship with the FSF” according to his blog. I spent time with him at the MySQL Users Conference last week. He is a fun guy to be around, and isn’t as US-centric as his remark “Last year, my family and I emigrated from Silicon Valley to Austin, TX.” would lead one to believe.

Barton is also an avid blogger. And, on top, a diligent podcaster.

As for blogging, he has recent MySQL relevant entries on partying …

Friday after MySQL Users Conference we had a smaller meeting at Google campus to talk about MySQL architecture mainly focusing on storage engine vendors and other extension areas.
It was very interesting to see all these storage engine interface extensions which are planned for MySQL 6.0 and beyond - abilities to intercept query execution or offloading query fragments and operations (sorting limit etc) in the storage engines. This is great news as this would allow to build really innovative storage engines with MySQL which was previously hard because of defined row by row retrieval interface and nested loops used for joins.

However what stroke me is a thought - This thing is really getting complicated. Few years ago Marten would frequently mention Oracle (and other commercial databases) as complicated beasts being overkill for most of their users.

Is MySQL becoming such a beast as well ? Will MySQL be able to …

I originally posted this as a follow-up to an (off topic) post on a discussion group about forming a community driven MySQL conference system. This is a more appropriate forum for the discussion.

What I'd love to see is something like a centralized repository and web site that could accept patches from various users. Other users could then select the patches individually and receive a custom patched source tarball (and perhaps binaries but probably not at first) for testing. These users could then select a more stable (ie production ready) build including only patches that have been well vetted.

By voting for particular patches, the community itself could decide what features are included in an 'official' community supported build, while still providing flexibility for those who don't want to have to manually merge multiple patches for custom builds.

Named builds would be another feature where a user …

That week at the conference was a busy week for me - as busy as any developer meeting I have had with MySQL in recent years. I had a great time seeing old faces again and it was much like old times talking, chatting and coding with them. In particular, I spent much of my time with Patrick Galbraith, Eric Herman and Arjen Lentz.Great progress was made: I worked with Patrick getting my ancient

MySQL Version 6.x is alpha. This blog is about its new features.

Expect a new article every week or two.

The first article,
MySQL 6.0 Feature #1: Supplementary Characters
is out now.
http://blogs.mysql.com/peterg/2008/04/