Progress on the Open Source enterprise grade MySQL monitoring system;  the schema for Monolith version 2 has been designed. Due to the many suggestions for features and the interest it has received I’ve put this on the front burner. That said, here is some more info on the next steps I’ll be taking.

• Monitored servers will use a command line agent (called remotely) to pull information from both MySQL and the OS.
• Historical information will include all values from global status and global variables, as well as CPU/Memory/IO/Disk usage.
• Standard graphing functions - the ones in the list from the previous post - will gather information from various view tables that contain historical data that is collected from the agent script. User defined graphing will allow you to look at historical values over time for any of the various global status or global variable settings (integer based ones anyway). …

Peter wrote a post a while ago about choosing a good InnoDB log file size.  Not to pick on Peter, but the post actually kind of talks about a lot of things and then doesn't tell you how to choose a good log file size!  So I thought I'd clarify it a little.

The basic point is that your log file needs to be big enough to let InnoDB optimize its I/O, but not so big that recovery takes a long time.  That much Peter covered really well.  But how do you choose that size? I'll show you a rule of thumb that works pretty well.

In most cases, when people give you a formula for choosing a configuration setting, you should look at it with skepticism.  But in this case you can calculate a reasonable value, believe it or not.  Run these queries at your server's peak usage time:

…

...has just been released:

You can download the GPL source distribution here. The config tool has been updated to use the new version.

Important things in 6.3.19:

• MySQL Server 5.1.29
  
• Faster --initial
• Undo logs and data files (disk data) is created faster. Now 512K is written at a time instead of 32K.
  
• New config parameter: InitFragmentLogFiles=sparse|full (you can choose if you want sparse redo log files or zero filled (full)).

For a full change log please see the reference manual.

To …

I have the pleasure to invite the Ukrainian and Russian MySQL communities to three events in the upcoming weeks, all of which I am attending myself.

Firstly, there is the Sun Microsystems ISV partnership event in Kiev on Wed 26.11.2008 from 10:00-18:00. The program for this event is published on my Russian language blog. Please register for this event through an email to Svetlana.Kovtun@Sun.COM.

Second, right after the ISV partnership event, we have a MySQL community get-together in the Sun offices within a 15 minutes walk. We’ll talk about MySQL and Sun, the integration status and plans, at 18:30-20:00. I hope to get several of the former MySQL employees, current Sun employees, attending. As a community …

Dear MySQL fans, 

we have done many webinars in these months with good attendance. While thanking everyone for participating, it's my pleasure to announce that now everything has been published and available on demand. You can download a webinar and watch it offline in case you have missed it or you like to view it again. Have a look at http://www-it.mysql.com/news-and-events/on-demand-webinars/

See you soon! 

Dear MySQL fans, 

we have done many webinars in these months with good attendance. While thanking everyone for participating, it's my pleasure to announce that now everything has been published and available on demand. You can download a webinar and watch it offline in case you have missed it or you like to view it again. Have a look at http://www-it.mysql.com/news-and-events/on-demand-webinars/

See you soon! 

MySQL 6.0.8 has new interfaces for semisynchronous replication.

The interfaces make it possible to load components to ensure that all transactions are replicated to the slave before the users of the master gets acceptance of the commits.

The original code was developed by Mark Callaghan (Google) and Wei Li (Google). Zhenxing He (MySQL) ported the Google code to MySQL 6.0, extracted the functionality into pluggable components, and changed the code so that all storage engines are supported. Paul DuBois (MySQL) wrote the MySQL manual documentation.

The extraction of this patch into components is a first step in our strategy to make MySQL Replication modularized with separate loadable components for special replication functionality. With more interfaces to the server, it becomes easier to make the server behave in …

I have measured the time it takes to do some operations with Cluster (6.3.19, which is about to be released very soon - you should upgrade) with respect to the disk, like starting it, creating table spaces etc.

Below all of this you can find the setup I used.

Initial start of Cluster (40GB of redo log files):
6.3.19: 3min 27sec

Create a 20GB undo file:
6.3.19: 6min 17sec

Create a 128MB data file for the tablespace:
6.3.19: ~3 sec

Insert 1M records a' 4096B (1 thread, batches of five):
6.3.19: 286 sec (3721.12 QPS)
(we can probably provision faster with bigger batches or more threads)

I then provisioned another 4M records (total of 5M records in DB).

Evil test: 100K Random reads (read 4096B) (5M records in DB):
6.3.19: 1290.42QPS (20 threads, io util is ~90% so we are almost completely io bound). So …

I have written about MySQL Query Browser and MySQL Administrator in my article: A graphical way to MySQL mastery on Linux.com

PS: All my writings are archived here at http://amitsaha.in.googlepages.com/writingsandtalks

I have written about MySQL Query Browser and MySQL Administrator in my article: A graphical way to MySQL mastery on Linux.com

PS: All my writings are archived here at http://amitsaha.in.googlepages.com/writingsandtalks