I just found post by Kevin, in which he criticizes Master-Master approach, finding Master with many slaves more optimal. There is surely room for master-N-slaves systems but I find Master-Master replication much better approach in many cases.

Kevin Writes "It requires extra hardware thats sitting in standby and not being used (more money and higher capital expenditures)", I'm surprised why would it ? Typically you can use both nodes for most of the reads, and this is in fact use pattern MMM was designed for.

"There's only one machine to act as the standby master. If you have 10 slaves you should be able to fail five times and still be operational." This is valid consideration but honestly for most of applications it is …

Another anecdote from the ongoing Java 1.4 to Java 5 transition... Last time it was an incarnation of "Favor composition over inheritance". This time I am writing about a multi-threading issue which can be equally subtle and difficult to pinpoint.

On the test systems we have set up we observed two strange types of exceptions at seemingly random times and in various different areas of the application. They looked similar to the following two patterns:

• java.lang.ArrayIndexOutOfBoundsException: 432
          at sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate(BaseCalendar.java:436)
          at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2024)
          at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:1941)
          at java.util.Calendar.setTimeInMillis(Calendar.java:1066) …

Another anecdote from the ongoing Java 1.4 to Java 5 transition... Last time it was an incarnation of "Favor composition over inheritance". This time I am writing about a multi-threading issue which can be equally subtle and difficult to pinpoint.

On the test systems we have set up we observed two strange types of exceptions at seemingly random times and in various different areas of the application. They looked similar to the following two patterns:

• java.lang.ArrayIndexOutOfBoundsException: 432
          at sun.util.calendar.BaseCalendar.getCalendarDateFromFixedDate(BaseCalendar.java:436)
          at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:2024)
          at java.util.GregorianCalendar.computeFields(GregorianCalendar.java:1941)
          at java.util.Calendar.setTimeInMillis(Calendar.java:1066) …

Thanks to Vanessa Fox (nude!) [1] for tagging me in the latest Friday blogging meme.

Here are my five reasons for blogging, with very little deep thought:

1. I like to write. Hell, I even wrote a book once and you can read all about it on that outdated website.
2. People actually read this stuff. Seriously. I don't know who most of you are (just some of you), but I appreciate the fact that I'm able to entertain, annoy, or otherwise occupy bits of your free time. It makes me feel loved (and hated).
3. It's a very efficient way to cause trouble, …

In many Search/Browse applications you would see main (fact) table which contains search fields and dimension tables which contain more information about facts and which need to be joined to get query result.

If you're executing count(*) queries for such result sets MySQL will perform the join even if you use LEFT JOIN so it is not needed which slows down things considerably. In similar way MySQL generates full rows while executing queries with limit before throwing them away which makes queries with high offset values very expensive.

To get better performance you can "Help" MySQL and remove JOIN for count(*) and do JOIN after limiting result set for retrieval queries.

Lets look at following simple example with one dimension table. In real life you will usually have several of these so performance improvements can be even higher.

PLAIN TEXT SQL:

1. CREATE TABLE `fact` (
…

mysqlsla (MySQL Statement Log Analyzer) v1.5 is finally done. Some people may recall a semi-release of v1.4 a few months ago, but that version wasn’t documented or otherwise mentioned at hackmysql.com.

Now, the real next release of mysqlsla is finished, and with documentation too! (However, I have removed the guide for now; it still needs to be completely rewritten). From the old v1.3 to the present, a lot has changed due to a lot of feedback, suggestions, problems, and bugs reported from users. Essentially, the script has been completely written, but here is a brief list of the changes:

• COMPLETE redesign from v1.3: more simple to use and more informative
• Log types are now mutually exclusive (but multiple logs of same type can still be …

So, recently I returned from a long trip where I was speaking at universities in the US and Canada. It was a great trip; I met a ton of folks in the academic and business community. However, the trip left me physically drained and a bit behind on my conference planning duties (of which there are plenty). But hey, I'm back now, and the conference team is kicking into overdrive. This week, the MySQL conference program brochure was finalized, and I have finalized the entire conference session schedule.

The schedule is 100% full. That's right. Not a slot available. Chock full of techie goodness, keynote craziness, tutorials and Birds-of-a-Feather sessions. In fact, there are more technical sessions in this year's conference program than any previous year and more than OSCON, LinuxWorld, and other major OSS …

Don Seiler has published the 39th edition of Log Buffer, the weekly review of database blogs, on die Seilerwerks. As always, please see Log Buffer’s homepage to learn more about contributing. Here’s Log Buffer #39.

While this site is meant to promote Bigfix's line of network management products, they've taken a swipe at the agressive tactics of typical software salespeople with the launch of their faux "Software Truth" site.  In what purports to be a congressional investigation with subpeona'd sales reps squirming under bright lights you hear a sales rep confess: "The truth is we don't have flexibility...it's like a corpse after 6 hours of rigor mortis has set in."

• BigFix: SoftwareTruth, Press Conference, …

In a few weeks I'm headed out to my 4th MySQL Conference. Typically I get all my travel/lodging set up way in advance but this year is different and I just got the last piece into place today. Yikes!

I haven't had much time this year for pre-conference MySQL posts, which tend to get more frequent leading up to the conference. I guess there is still two full weeks to get back into groove before I head out.

I'm looking forward to the conference for a few reasons (in no particular order):

• 
  
• Presentations: I'm excited for a number of presentations on the schedule. As I look back over the years I think the thing I've enjoyed the most in presentations is hearing how other folks are using MySQL to solve their data storage/access problems. My first conference in (Orlando, 2004) very heavily featured the work …