I'm sitting in Kaj Arnö's Cloud Computing Shoot Out here in the MySQL Confernce & Expo. Great panel, great discussion! The important question, always, is about business models related to storage vs. compute clouds.

On Tuesday at the MySQL Camp 2009 in Santa Clara I presented Setting up MySQL on Amazon Web Services (AWS).

This presentation assumed you know nothing about AWS, and have no account. With Internet access via a Browser and a valid Credit Card, you can have your own running Web Server on the Internet in under 10 minutes, just point and click.

We also step into some more detail online click and point and supplied command line tools to demonstrate some more advanced usage.

Getting started with MySQL in Amazon Web Services View more presentations from Ronald Bradford.

I see three stages in the adoption and the evolution of the adoption of cloud computing:

1. Taking an existing application, and transferring it as is into a cloud provider. This is "forklifting".

2. Taking an application, and wrapping it up in cloud based provisioning and backup. This is the business space that RightScale and Zmanda help with.

3. Developing applications that implictly assume they are running in a cloud environment. I see a lot of talk of this, but not all that many running yet. But very soon they are going to be everywhere.

Curt Monash of DBMS2, the database industry analysis and research blog, posted a flurry of Oracle/Sun/MySQL commentaries since the announcement, and upon learning that they no longer appear on PlanetMySQL I thought I would quickly draw the community’s attention to the thoughts of one of our industry’s most respected thinkers on the deal. It is [...]

110 exams delivered on the first day of the UC! That was despite Wifi Saturation. O'Reilly has provided a few more 'hard line' to help fight the problem.

Exams are in the Magnolia room (opposite the Hyatt registration desk, jut past the escalators) from 8:00 AM to 3:00PM. And the cost is still $25!

Slides:
http://www.technocation.org/files/doc/2009Keynote.pdf

References:
I am @sheeri on twitter
My blog is at http://pythian.com/blogs/author/sheeri
My e-mail is cabral@pythian.com

Pythian became the first ever Sun Enterprise Remote DBA Partner — read the details at http://tinyurl.com/pythiansun.

Technocation, Inc can provide free web space for slides, videos and audio files. Their website is and you can e-mail them at info@technocation.org Technocation, Inc. is a 501(c) not-for-profit US corporation dedicated to providing educational resources for IT professionals.

…

For some reason my presentation slides have not been posted to on MySQL Users Conference site. Here it is, a pdf format of "Introduction to Using DTrace with MySQL".

The presentation slides for my Query Analysis talk here at the users conference are now available:

How I Used Query Analysis to Speed up My Applications

I’ll sort out the scripts and bits and pieces I use once I get back to the office next week, for those people waiting for that material.

My presentation slides for the Scale Up, Scale Out and High Availability tutorial here at the MySQL Users Conference are now available for download:

Scale Up, Scale Out and High Availability: Solutions and Combinations

These have been on the MySQL Conference website for days now, but for some reason they don’t seem to have been freed yet.

To those waiting I’m sorry for the delay in getting these uploaded.

In InnoDB there is an implementation of both mutexes
and RW-locks. The RW-locks implementation have been
improved by the Google SMP patches. Both of these
implementation relies on spin-loops as part of their
implementation. The defaults in InnoDB is to check
the condition, if it's not ok to enter to spin for
about 5 microseconds and then come back to check the
condition again.

If one reads the Intel manual how to do spin-loops
they propose to use a PAUSE instruction and then
check the condition again, so a much more active
checking of the condition. When we tried this out
using the sysbench benchmark we found that using
the Intel approach worsened performance. So instead
we tried an approach of putting the PAUSE instruction
into the InnoDB spinloop instead.

This approach turned out to be a success. Even on
machines with only one …