Hooray! The MySQL reference manual has a new search system. It now uses a Google Appliance and the results should be a lot better. The old system was not very helpful. It used to break config variables into multiple words and search on them individually and give a billion results I didn’t care about. I’ve just tried to search for some things like key_buffer_size and got results I think are very useful.

The following Lua scripts are the examples are from my MySQL Proxy @ OSCON 08 presentation.

analyze_query.lua

MySQL Proxy Analyze Query.

Requires MySQL Proxy Logging Module.

What is released is the Version for MySQL 5.0. A generic version for all MySQL versions is not yet released.

histogram.lua

This script is part of the standard MySQL Proxy examples.

Other Scripts

Additional Lua scripts from MySQL forge are available here.

MySQL Proxy got a bunch of changes in the svn-repo over the last weeks. Most of the important changes are in and we are working on making it a good 0.7.0 release.

The important changes are:

• script cache to improve the proxy performance
• central low-level decoding + lua wrappers
• plugins for proxy, admin and debug
• admin plugin is now lua based (more flexible)
• improved test coverage
• close a connection where we did throw a assertion before

Script Cache

In 0.7.0 we added a script-cache to only reload a script when it has changed and use a byte-cached version of it if it is unchanged.

This speeds up all script functionality quite nicely. No extra compile step as we did in 0.6.x when a connection was opened.

Plugins

We moved the proxy functionality into a plugin that can be loaded at startup as needed. We have at …

The following Lua scripts are the examples are from my MySQL Proxy @ OSCON 08 presentation. analyze_query.lua MySQL Proxy Analyze Query . Requires MySQL Proxy Logging Module . What is released is the Version for MySQL 5.

I have completed a rough draft of the first chapter of "Drupal Performance and Scalability". The first chapter of this online book is divided into four sections, the first of which focuses on the importance of fully defining your performance and scalability goals, helping you to identify what you need to accomplish and how to set concrete and attainable goals. The second section discusses monitoring and measuring your ongoing progress, helping you decide what you need to monitor, and how to monitor it. The …

Sunday morning, and I couldn't help but ponder Michael Tiemann's excellent note on Microsoft's revised (and improved) Open Specification Promise and "what Microsoft can do for open source."

Michael rightly notes that Microsoft's Promise, while certainly improved, still leaves much to be desired. No surprise there, which leads Michael to a thoughtful, probing analysis of what Microsoft could do to fully engage with open-source communities:

Let's think big. The open-source community already has more than a billion lines of source code at its disposal, and it's doubling every 12.5 months, so I think it's fair to say "we don't really need your code." And we also know that money alone is no substitute for the freedom to innovate that we so crave. So what big thing could we do with Microsoft's …

Looks like the guys over at Amazon had fun this week:

We’ve now determined that message corruption was the cause of the server-to-server communication problems. More specifically, we found that there were a handful of messages on Sunday morning that had a single bit corrupted such that the message was still intelligible, but the system state information was incorrect. We use MD5 checksums throughout the system, for example, to prevent, detect, and recover from corruption that can occur during receipt, storage, and retrieval of customers’ objects. However, we didn’t have the same protection in place to detect whether this particular internal state information had been corrupted. As a result, when the corruption occurred, we didn’t detect it and it spread throughout the system causing the symptoms described above. We hadn’t encountered …

So it seems MySQL got on the radar of the monopolist, but the quotes that came from that event are more interesting .

Over at Oscon2008 Oscon people started realizing that the old monopolist definitely isn't the one to be afraid of.. there's new ones out there..

I already got quoted in a local magazine on the fact that new startups are more looking to Google than to redmond, but it also seems that Apple is the new kid in town to envy.

However, when looking at the Linux desktop I think we shouldn't be trying to imitate anybody .. we should be trying to head the pack, just as we have already done with Vitualization and other technologies.

Julian Cash is well known, among other things, for being the photographer of the open source communities, as you can see from his photo stream, or this picture of his newest book.

For more books, you can look at The human creativity project.
At OSCON 2008, participants could attach one or more ribbons to their badge, to state their affiliation with a project or an idea. When the sought ribbon was not available, there were blank ones that users could fill with their favorite topics.
As you can see here, I made free use of the ribbons. Julian Cash, instead, stated his affiliation with Perl quite strongly.
…

At OSCON this year, MySQL's Brian Aker made this bold statement:

Microsoft is irrelevant....We're more worried about Apple.

Perhaps he was taking a cue from MySQL's Zack Urlocker, who has been buying Macs for family members, but I understand the sentiment. Microsoft still dominates the desktop, but the momentum is Apple's.

Perhaps this is why the Free Software Foundation, which wants to protect everyone's freedom (except, oddly, on the web), has gone on another Quixotic campaign to save the world from Apple's DRM (Digital Rights Management) by …