The JAX Innovation Award is intended to honour and recognise the most remarkable and outstanding European contributions in the world of Java and Eclipse. These contributions can include products, open source projects, ideas, concepts, publications, or break-through technological innovations. What's your most favourite innovation or project?

You can submit your proposal online or by downloading and filling out forms provided from this page. The winner can win a 10kEUR prize, which will be presented during the JAX, Enterprise Architecture, and Eclipse Forum Europe …

I just started QueryBrowser on my SuSE 10.0 PC (the version that's installed by default) and wondered, what version it would be. Looked into Help/About and was extremely surprised to see 1.2.7 as version number.

The current Linux version of QueryBrowser as stated on dev.mysql.com is 1.1.18.

I guess that the version number of QueryBrowser's Help/About dialog is wrong, but does somebody know exactly, what happened here?

Maybe this message looks like a little late for you, but for me it's true. Today I finally got an xDSL internet connection, which starts a whole new epoch for me.

So far, I only had an ISDN connection with a maximum transfer rate of 7 - 8 KB/s. Every 8 hours, the line has been disconnected automatically, so no big downloads were possible - and even smaller downloads made it impossible to surf through the web comfortably. That was extremely limiting and there were many things that I could only dream of.

Now, these times are over! Today I have already downloaded more data than I usually did (or could) in a whole month before - I'm just installing SuSE Linux 10.1 Beta9 in a VMWare server (both just downloaded), and Ubuntu 5.10 is almost finished. Many more things are planned - also to take a close look at MaxDB, as it won't be a problem anymore to quickly download all the things that I need. Downloading new versions of …

We’ve published the first few episodes of the weekly MaxDB series in .pdf form. Please take a look and let us know what you think!

MySQL AB :: The MaxDB series on PlanetMySQL.

© cjcollier for C.J.'s WordPress of studlyness, 2006. | Permalink | No comment

Add to del.icio.us

Search blogs linking this post with Technorati

Want more on these topics ? Browse the …

Hey all -

Finally got my “MySQL In-Depth for DBA’s” presenation ready for the big upcoming User’s Conference. I’m looking forward to going over all the nitty-gritty that DBA’s need to know with respect to being as successful as possible with MySQL in their shop. Because I’m a big believer in designing for performance, I’ll be spending a good chunk of time on how to build the right design for the job. Of course, this goes beyond just physical database design, and runs down the path of picking the right security model, the right High-Availability implementation, and much more. We’ll also be spending time on how to focus on the right things when it comes to monitoring and tuning performance. And I’ll be sharing a sneak peek into upcoming MySQL features that every DBA will want to know about.

So if you’re a DBA, or a developer who’s been forced to tackle both your development and the DBA’s job, make sure you …

No, we didn’t forget about Make MySQL 5.1 Rock contest. We were just migrating our bugs database, and going through a little teething problems everytime a Monday hit! (yes, I’ve not been taking them for myself in the last two weeks!) The good news is that, you get an additional fortnight to win yourself an iPod Nano.

This week’s winner is none other than Mike Kruckenberg. He’s submitted a bunch of bug reports, in relation to MySQL Cluster (another hot topic these days), and one that caught my eye was a critical server crash (mysql#18603). He also blogs about his day spent with MySQL 5.1, which is a fun read.

If …

ok.. now this is getting stranger.

I have 2 windows open, in one I get

$ mysqlslap --use-threads -psunfire -c 90 -i 500
Benchmark
        Average number of seconds to run all queries: 2.180 seconds
        Minimum number of seconds to run all queries: 0.779 seconds
        Maximum number of seconds to run all queries: 4.497 seconds
        Number of clients running queries: 90
        Average number of queries per client: 0

and in the other i get

$ mysqlslap --use-threads -psunfire -c 90 -i 500
Benchmark
        Average number of seconds to run all queries: 0.012 seconds
        Minimum number of seconds to run all queries: 0.002 seconds
        Maximum number of seconds to run all queries: 0.015 seconds
        Number of clients running queries: 90
        Average number of queries per client: 0

same machine, same user-id, same binary. the only difference is that mysql started in the ‘fast’ window.

MySQL Users Conference 2006 is now in close proximity and I'm working hard preparing my presentations.
I've got 3 ones this year. All should be very interesting one but challenging to prepare.


First one is MySQL Performance Optimization Tutorial, which I'm doing with Tobias. It is kind of sounding similar to what I've been doing last year
but it is a lot different in the content. Frankly speaking we did not recycle any of the old stuff and just wrote everything from scratch. To learn from
previous year mistakes we now have it more condensed so we can cover everything in short 3 hours, as well as keeping it much more practical. Based on My and Tobiases experience of performance optimization of real application we kind of provide how to or insight on how we work, what exactly do we do, why and how we do it. For particular application there are of course much more specific tricks which can be played but at …

I am writing an article about some advanced replication features (coming soon), and I wanted to measure the speed of each specific architecture I am working with.
There seem to be no builtin MySQL solution for this particular problem, and thus I am using a hand made metrics tool, inspired by something that Jeremy Zawodny suggested in his High Performance MySQL a few years ago (see the relevant chapter on replication with code).
The naive method would be to set a timestamp in a master table, and to measure the same record when it shows up in the slave. Unfortunately, (but correctly, I have to say!) this does not work, because the binary log includes information on the current timestamp, so that master and slave in the end …

Zack Urlocker has posted a great parody pic on his blog. Go and see The Full Monty.