Here is the quick notes from the session Helping InnoDB scale on servers with many cores by Mark Callaghan from Google (mcallaghan at google dot com).

• we have a team now, to help scale MySQL to do the enhancements (9 people,  I hope yahoo management reads this)
• Overview
  • describe the problems on big servers
  • work done by InnoDB community
  • ask MySQL/InnoDB to fix the problems by taking the patches
• Community team
  • InnoDB/Oracle
  • Google MySQL team
  • InnoDB community
  • Percona - Peter and Vadim
…

The Future of MySQL by Monty Widenius and Jay Pipes.

• Why this talk
  • MySQL and Sun should become more transparent
  • Easier to discuss and act when you have facts
  • when user know the limitations, they know how to go around
• Threads
  • one connection/thread doesn’t work well
  • no priority threads
  • no way to ensure we have X threads
• Symptoms
  • Too many context switches
  • we are not using multi-core efficiently
  • does not scale that well after 4-8 cores
• Solution
  • –thread-handling=pool-of-threads (6.0) …

I've so far missed every single keynote and breakfast. Fortunately, all the good ones have been recorded.

I'm sitting here in Paul's PBXT talk, and it's really cool. It was really cool last year, and it's only gotten better.

When someone asks me about the various future MySQL storage engines, my answer always is "It depends on which is better for your load. Maria or PBXT, or both?"

Final slides from keynote delivered this morning at the MySQL user conference. Topic was protecting live MySQL databases.

(Slides render well in both OpenOffice and PowerPoint)

This was my reason #1 to attend the UC and it lived up to my expectations!
The Lost art of the self join was a truly enjoyable experience. Beat Vontobel delivered with confidence and humor a talk about a subject that most people would consider dull.
It was a feast for all attendees with an inclination for hacking.

The truly amazing thing in this presentation was not that Beat explained how to solve a Sudoku puzzle with one query which is a truly amazing feat, but that he explained how to use the join mechanism to implement a backtracking machine, similar to a regular expression algorithm.
The presentation was concluded with a live solution of a 6x6 sudoku puzzle. The reason for not using a 9x9 puzzle is …

Watching the MySQL uproar unfold brings to mind an array of random thoughts:

1. Microsoft really should acquire an open-source company. It would get credit for opening up, even if it closed off some parts of whatever project it acquired. Sun...? It's getting lambasted for no logical reason at all. It's not as if MySQL wasn't actively considering tweaks to its model before Sun acquired them, just as all open-source companies do. No one has settled on the exact right model yet.
   
2. While Microsoft and other "proprietary companies" move toward opening up, it would appear that there is some movement among "open-source companies" to close off. Maybe we'll meet in the middle?
   ...

I've been getting pings all morning about my thoughts on the Slashdot article:
http://developers.slashdot.org/article.pl?sid=08/04/16/2337224

Google reveals my thoughts on crippleware. I've never been particularly quiet on the subject of the "Open Source 2.0" branding cycle of trying to say that a "mostly free" open source project is open source. The entire movement of "mostly free" pretty much disturbs me.

I do not believe though that this subject is cut and dry. I am going to use Innodb as an example. I do not consider it crippleware, and I have been amazed and delighted at Oracle's ownership of it. They have made excellent stewards of the source code.

Do they have a closed source backup tool? Yes.

Do I have an issue with this? No.

Why not? We can use Innodb just fine …

My slides have just been uploaded for the talk I just gave at the MySQL Conference and Expo 2008 titled “Scaling out MySQL: Hardware today and tomorrow“. You can download them now as PPT and PDF.

Thanks for coming to my talk!

Mark started by making the point that when he talks about problems with InnoDB, he's referring to what he calls "blemishes on a beautiful work of art". In an earlier direct chat with him he explained that the InnoDB source code is well structured and documented.

People active on InnoDB are at Oracle/InnoDB (of course), a team (!) at Google, Percona (PeterZ & Vadim), and a few other individuals like Yasufumi Kinoshita (NTT Comware Corp).

A few days ago Oracle/InnoDB released a new version of InnoDB, refactored as a plugin engine, with a number of very interesting new features and improvements.

Mark also advertised some of the MySQL-related service businesses and tools (such as Maatkit), it turns out he's wearing multiple layers of shirts ;-) Indeed, Open Query's "Yes, I will tune your MySQL server." shirt is represented as well. Thanks Mark!
(if you're reading this at the conf, I have some shirts …

Here are the slides and links I am using for the “Database Security Using White-Hat Google Hacking” at the 2008 MySQL Users Conference and Expo.

pdf slides

Where to Start:
http://johnny.ihackstuff.com/ghdb.php

i-hacked.com/content/view/23/42

for the impatient

Google’s Terms of Service
Google Operators

More Googlehacks to run:
Page 35 of …