This release is part of the unstable 1.5 branch. Its features will ultimately go into the stable 1.6 branch. You can download it from the innotop-devel package.
The major change is I've ripped out the W (Lock Waits) mode and enabled innotop to discover not only what a transaction is waiting for, but what it holds too. The new mode that replaces W is L (Locks). My last article goes into more detail on this.
This article shows you how to use a little-known InnoDB feature to find out what is holding the lock for which an InnoDB transaction is waiting. I then show you how to use an undocumented feature to make this even easier with innotop.
This release is part of the unstable 1.5 branch. Its features will ultimately go into the stable 1.6 branch. You can download it from the innotop-devel package.
The major change is a new Command Summary' mode (switch to this mode with the 'C' key) that's similar to mytop's 'c' mode. It shows you the relative size of variables from SHOW STATUS and SHOW VARIABLES.
Version 1.5.0 of the innotop MySQL and InnoDB monitor is out. This release is the first in the unstable 1.5.0 branch, which will eventually become the stable 1.6 branch. I'm beginning to merge the various branches I've made to support some of our needs at my employer. This first release adds some major new features and prepares for some other large improvements and new features.
I mentioned earlier that I'd blog about progress on the book as we go. It's not only progress on the book itself -- I want to write about the process of writing, because I think it's very interesting and relevant to software engineering. I'm finding a lot of the work in writing a book comes from some of the same things that make software hard: coordinating work, deciding what should go where, and so on.
This release of MySQL Toolkit fixes some minor bugs and adds new functionality to four of the tools. Some of the changes I made were in response to feedback I got at the recent MySQL Camp. I'm still working on some of the feature requests, such as daemon-izing certain tools.
For those who requested features for MySQL Query Profiler, the tab-separated format should give you the desired output: no zero rows, and variables are not renamed.
RPM packages for innotop, a flexible and powerful MySQL and InnoDB monitor I wrote, are now available through the openSUSE buildservice, which builds RPMS on several platforms. Thanks to Lenz Grimmer, SUSE Linux, and Dr. Peter Poeml for making this happen.
We've begun writing the second edition of the now-classic High Performance MySQL. "We" means co-authors Arjen Lentz, Baron Schwartz, Vadim Tkachenko, and Peter Zaitzev. O'Reilly is still the publisher, and Andy Oram is still the editor. With a team like this, I think the second edition will be a book you don't want to miss. Though in theory we're revising the first edition, the truth is we're starting from scratch and re-writing the book, and significantly expanding it at the same time. A lot has changed since Jeremy and Derek wrote the first edition. Today's MySQL deployments push the limits further than many people thought possible a few years ago. We'll teach you how they do it.
I'll be speaking on using Drupal with Adobe technologies such as Flex, AIR, and Flash. The event is totally free but you must register.
A high-performance application that has producers and consumers
of some resource, such as a queue of messages, needs an efficient
way to notify the consumers when the producer has inserted into
the queue. Polling the queue for changes is not a good option.
MySQL's GET_LOCK() and RELEASE_LOCK()
functions can provide both mutual exclusivity and notifications.
This post was prompted by a message to the MySQL general emailing list some time ago, but I'm finally getting around to actually testing the theoretical solution I mentioned then. I can never just think my way through anything that involves locking and waiting... I have to test it.