We’re proud to announce that the new version of Kontrollbase is available for download. The enterprise MySQL database monitor and analytics application has been getting a lot of improvements and bug fixes since our initial beta release. Included in this release is an improved web-based installer, socket options for the client server connections, more troubleshooting solutions in the documentation, and some JSON fixes for form submission reporting. You can read more about the full features here: http://kontrollsoft.com/software-kontrollbase and download the new release here: http://kontrollsoft.com/software-downloads

If you are using the scripts from the Configurator (and yes, the broken link is now fixed so it is actually possible to get the config package..), and want to tweak your configuration on a started Cluster then you can do like written below.

There is also a new script in Configurator 2.2 (released 28th April 2009, PST1153AM , GMT07:53) that lets you check the values of different config parameters. Its use is described below.

Pretend we want to extend the DataMemory from 1024M to 1536M:

1. cd mysqlcluster-70/cluster/scripts
2. vi ../config/config.ini
   This is the master config.ini file and will be copied out to the management server(s). Don't change /etc/mysql/config.ini, as that will have no effect.
   
3. Set DataMemory=1536M …

Today we glad to announce release 1.0.3-5 of our XtraDB storage engine.

Here is a list of enhancements in this release:

• move to MySQL 5.1.34
• removed rw_lock patch, so we now use Google's rw_locks
• fix crash after upgrade 5.1.31 -> 5.1.33
• fix mysql-test

Percona XtraDB 1.0.3-5 available in source and several binary packages.

XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and …

A little challenge for you… given an existing app that does not know about separate master/slave connections, and you want to enable working in a replicated infrastructure. Simply redirecting all SELECTs to the slave connection will not work. Why?

Hint: there are at least two reasons, depending on other factors. There may be more.

Comments are set to be moderated so providing answers will not spoil it for others. I’ll leave it run for a bit and then approve all comments.

I saw something interesting today when helping out someone on the #mysql IRC channel. It was a cnf file that was designed to destroy a server. Before I get into the why-not, here are the goods:

...snip...
read_buffer = 128M
join_buffer = 128M
key_buffer = 512M
max_allowed_packet = 200M
thread_stack = 192K
thread_concurrency = 8
thread_cache_size = 64
query_cache_limit = 256M
query_cache_size = 256M
table_cache = 8192
query_cache_type = 1
sort_buffer = 128M
record_buffer = 128M
myisam_sort_buffer_size = 128M
thread_cache = 64
max_user_connections = 500
wait_timeout = 200
max_connections = 4096
tmp_table_size = 1000M
max_heap_table_size = 1000M
...snip...


Now, you may ask why these settings are bad. I will tell you. First, an equation for calculating per-thread …

OIN aims to cut the FAT. What is the point of the GPL? Black Duck takes flight. Ingres delivers Salesforce.com appliance. The ongoing fallout from Oracle-Sun. Feedback on the Bee Keeper model. And more.

Follow 451 CAOS Links live @caostheory

OIN aims to cut the FAT
# The Open Invention Network announced plans to review the Microsoft FAT patents at the center of its recent skirmish and settlement with TomTom. have been placed for prior art review on the Post-Issue …

Last week I delivered a talk titled "MySQL and Search at Craigslist" as part of the 2009 MySQL Conference and Expo. I talked about some of the good and bad of our MySQL work and also talked a lot about our recent Sphinx deployment. The slides are embedded below and here, thanks to SlideShare. (Anyone know why Google Docs doesn't yet handle OpenOffice presentations?)

MySQL And Search At CraigslistView more presentations from jzawodn.

…

There have been ongoing rumors about a license change of the MySQL documentation. Karen Tegan Padir even asked the audience during her keynote at the MySQL Conference last week. Some liked it, but we didn't experience any overwhelming positive feedback. Currently, the MySQL Reference Manual and other MySQL documentation are released under regular copyright. Note, however, that Sun grants permission to use the docs in many ways that don't require written approval.

Most people in open source land believe that if the software is free then also the documentation should be (this is, for example, stated by the Free Software Foundation, in the preamble of the GNU Free Documentation License).

I agree with that …

Just to clarify, this is a comparison of Calpont performance against the BKA performance.  Calpont uses a multi-threaded, distributed hash join operation rather than an index operation, and so does not use the BKA access directly.  Note that the BKA performance enhancement clearly is the right direction to improve index operations.  This comparison just shows the power of hash join for big data.

Result graphed.  Note that the graphic contains multiple comparisons with differing conditions. 

The first 2 metrics come from the 2008 UC presentation, the third a Calpont run at a scale factor of 1 (6 million rows in lineitem table), and  are disk runs.  Calpont is configured with one performance module.

The next 2 metrics scale the number of rows by 10x, and 100x with Calpont timings, again disk timings, and again 1 performance module.

The next metric used sf100 (600 million rows in …

One of my favorite projects in the MySQL community is, of course, Drizzle. In fact, if I had to rank these sorts of things, I would say PBXT is my favorite project, with Drizzle being a very close second. There's plenty of reasons why, but the biggest thing that attracts me is that Drizzle can be anything to everyone. It often gets branded as a Cloud DB, and while Cloud is a big piece, it's really side-stepping the whole point. What makes it so enticing in the Cloud is what makes it enticing for everyone else too.

Namely that they took MySQL, threw out all the bad, scrapped off all the cruft, and ended up with a beautiful, small, simple database platform. That, in it is itself, doesn't do it for me. Granted, they removed some ugly features of MySQL such as sql_mode and are moving towards transactional engines being the default …