So as one of the last speakers, I finally got the opportunity to hold my talk on PHP6. You can find the pdf in my slides section as always. I was actually positively surprised that the room was fairly full, considering that I had seen several people head off to the airport already. I first asked how many people are still on PHP4 and a fair number raised their arms. Anyways, for some reason I felt that I was not speaking as fluent as I can, so I am a bit disappointed with my performance as a speaker. The slides however are probably the most complete resource for people who want to mentally prepare themselves for PHP6. One note of warning though: During my talk I noted that any of the changes/features listed …

Frank asks us to vote on his Barcamp presentation. I also asked to do so on the Barcamp site

For Frank my vote is on the "Rails doesn't scale topic", (I'd say OpenID but I guess I misunderstood Pascal saying he'd do something on that yesterday)

But as I see that lots of people are looking at how to use MySQL and scale it I'd figure maybe I should do a talk on MySQL Cluster , so send in the votes !

I missed a couple of talks that I’d really have liked to attend, for various reasons (probably the fact that at the MySQL conferences, staff also have a tonne of meetings and customers/people to meet). Thanks to the great bloggers, I don’t feel so bad for missing such talks. And for the ones with no blogs and notes, well, I’ll just hope and dream up the fact that sometime in the future, there will be video recorded sessions, available on the same day on the Internet, in OGG (like was done at linux.conf.au 2007).

Eric Lai has an interesting article in ComputerWorld titled: How Digg.com uses the LAMP stack to scale upward. And Mike Kruckenberg had some of his notes, which I think are also useful. Considering Digg.com …

The conference is now over and I am glad it is. It was an intense four days of information exchange and meeting interesting people. The feeling I now have is twofold: One end says: "Woohooo! That was great, got to do that again."; The other is: "But not anytime soon!". Thanks to Jay Pipes for putting a lot work into making this happen.

And special thanks, of course, to Jeremy Cole and Eric Bergen of Proven Scaling who spent some serious coin to have J.R., Carlos and me attend. You rock!

I couldn't find an official announcement, but there will be a MySQL Conference in Tokyo later this year. Now, what talks could I submit for that? :-)

Adam Donnison hosted a session about how the *.mysql.com websites are architectured. He explaind how the situation was before they started building the current implementation and showed several drawbacks with that approach (Apache and MySQL on the same machine, no failover) and how they fixed it. He even showed how well the new MySQL Monitoring solution works without noticing that while he is showing live data, that the monitor reports a peak of requests and several red (dangerous) areas in the system. The site went effectively down when he explained how easy all this is to manage. He got very busy when we notified him, but he actually got everything up and running again within a few minutes.

MySQL 5.1 comes with a new feature called Events. This is effectively a user-friendly cron-mechanism built into MySQL. Very nice. Other goodies can be found in the manual.

I had the pleasure to say Hi to Duncan Davidson, O'Reilly's conference photographer. Check out his flickr Photo Set. He's got some impressive shots up. An he's a really nice guy :-)

Rasmus, in both his session and his keynote, painted a very good picture of the state of security of current web applications. Namely, there is none. Even if you make your website as secure as possible, an attacker is able to use your users and their out-of-date (or even current!) software to steal data and brake into systems.

"The web is broken you can all go home now."

This has nothing to do with a certain database vendor. Paul Tuckfield of (first) PayPal and (now) YouTube fame described a nifty method to speed up MySQL Replication in his keynote at the MySQL Conference.

The pitch is simple: He implemented an oracle algorithm. In more detail: In a MySQL setup, several layers of caches exist. In front of the database sits the query cache that saves the MySQL from doing actual work (query analysis, execution, disk I/O). The next two levels sit between MySQL and a the actual disk. The first is the filesystem cache that the operating system provides. The second is the block-level cache that the RAID controller provides. Considering the last, from a MySQL point of view, data has been written, when it hits the RAID controller.

All these caches serve one purpose: Reduce execution of complex or slow operations such as physically reading data from a harddrive or writing to it. MySQL Replication, in a …