An hour ago I ended my 45 minutes MySQL Cluster Introduction talk at the Free and Open Source Software Conference (FrOSCon). I tried to really make this a compact, more or less complete overview. Apparently it worked!

MySQL Cluster is quite a beast to talk about. Doing this in 45 minutes, with 15min extra for questions, is not an easy task. You can check my presentation on the FrOSCon website of the presentation. I was troubled about the order of things, for example should I talk about components first, do the overview later? I feel it is OK as it is right now, though I have to cut a bit for making it shorter, and clearer.

A feedback after the talk was that I needed to touch the fact that Cluster is not really functional on Windows (yet). This made me think I indeed missed some nice information here and there.
Another comment from …

Right now I am in Skien, which is somewhere in the middle of the dark forests of Norway. Skien, a bustling town of a whopping 45.000 people is the seventh largest municipiality in Norway, and also the home of the PHP Vikinger Unconference.

My part on this Unconference was to hold a Nontalk, a session where I asked the audience to come up with things that they think are typical for Everyday PHP use and that currently do not have a name.

The following stuff are the slightly edited and commented notes I made in front of the audience while moderating our session.

Continue reading "phpvikinger.org: Things that have no name"

I’ve introduced a new design and Wordpress backend at www.vbmysql.com, feel free to take a look and provide feedback. Now that editing will be easier I think I’ll be pushing out some fresh content too.

MySQL doesn't allow referring to a table that's targeted for update in a FROM clause, which can be frustrating. There's a better way than creating endless temporary tables, though. This article explains how to update a table while selecting from it in a subquery.

I frequently get questions along the lines of "how many transactions per second MySQL can do" or "how many servers I need to handle 100.000 users" or "which hardware would be enough to handle my 40GB" database.

There are two things which are very interesting about these questions which make them funny and annoying at the same time

1) People asking these questions demand the answer. It could be internal Sales and Marketing people or even customers saying they typically get the answers from other vendors.

2) The best answer to this question will not be a number but something like "it depends". Seriously you need much more information than given in this example to give estimate which is correct at least to the order of magnitude.

Seriously in MySQL Consulting practice it would not be exception to have 1-2 orders of magnitude performance increase just by proper tuning - this means even application implementation …

I've been listening to a number of podcasts when I'm in my car. One of my favorites, This Week in Tech (or "TWiT" as its known) hosted by Leo Laporte and featuring a case of regulars including Kevin Rose from Digg, John Dvorak, Patrick Norton and others.  Leo is clearly a fan of technology and his enthusiasm and self-deprecating humor while reviewing the week's tech stories makes for a good listen.

Recently, TWiT has spun off a new show called FLOSS Weekly (get it?) featuring Chris DiBona (pictured above), open source guru over at Google.  Although the first few episodes were a bit slow, it's now starting to find its voice.  Leo Laporte co-hosts many of the shows helping to provide a better balance and preventing the show from just being too mcuh of an …

I used XDebug to profile the behavior of Drupal, and to study the interaction with the database server. I aggregated the profile information of 100 requests to the main page using the "Apache, mod_php, PHP4, APC" configuration used for previous benchmark experiments. More information about my experimental setup is available at that page. XDebug generates a trace file with all the profile information which I visualized using KCacheGrind.

Drupal has a page cache mechanism which stores dynamically generated web pages in the database. By caching a web page, Drupal …

I used XDebug to profile the behavior of Drupal, and to study the interaction with the database server. I aggregated the profile information of 100 requests to the main page using the "Apache, mod_php, PHP4, APC" configuration used for previous benchmark experiments. More information about my experimental setup is available at that page. XDebug generates a trace file with all the profile information which I visualized using KCacheGrind.

Drupal has a page cache mechanism which stores dynamically generated web pages in the database. By caching a web page, Drupal does …