I just uploaded a new tarball for sar-sql containing a few bug fixes, overall code improvements. I also added options to get a partial snapshot of SHOW SLAVE STATUS and SHOW MASTER STATUS. I chose only a few columns to avoid over complicating the project.

I plan one more round of heavy code changes, but no new features until I can stabilize the code enough to release it as beta.


Feel free to visit the project page in Launchpad to comment on the Blueprints, report new bugs and participate through the Answers section.

Thank you very much to Patrick Galbraith who provided some ideas on the best way to solve some of the coding issues.

Enjoy the …

I posted about FusionIO couple times RAID vs SSD vs FusionIO and Testing FusionIO: strict_sync is too strict…. The problem was that FusionIO did not provide durability or results were too bad in strict mode, so I lost interest FusionIO for couple month. But I should express respect to FusionIO team, they did not ignore problem, and recently I was told that in last drivers FusionIO provides durability even without strict_mode (see http://www.mysqlperformanceblog.com/2009/06/15/testing-fusionio-strict_sync-is-too-strict/#comment-676717). While I do not fully understand how it works internally …

I had one of those situations today that I think every person working with IT experiences from time to time.  I had a problem that took 4 hours to resolve.  Once resolved I realized that doing the right things in the right order (and also memorizing a little better) could have saved me 3 hours and 55 minutes.

The problem was related to SQLyog HTTP-tunneling. When new PHP versions are released it is most often me that verifies that our HTTP tunneling is not broken.  Thus I have followed the PHP 5.3 release cycle from early betas to RC and GA and experienced that very early  PHP 5.3.0 beta  releases did not work with our HTTP-tunnel. However as both 5.3.0 RC and 5.3.0 GA worked fine (as every 5.2.x always did) I executed “SET panic = OFF” against my most important system (old but still a little functional!).

However the panic reoccurred when PHP 5.3.1 was released.  Nothing worked from PHP. I sat …

Palm sued for GPL violation. Wind River launches Android distro. And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca
“Tracking the open source news wires, so you don’t have to.”

For the latest on Oracle’s acquisition of MySQL via Sun, see Everything you always wanted to know about MySQL but were afraid to ask

# Palm sued by Artifex over alleged GPL violation.

# Bradley M Kuhn described “The Anatomy of a Modern GPL Violation.”

# Wind River …

Just a quick graphical presentation of the load rate with InfiniDB importing 23.9 billion rows in about 12 1/2 hours.  Rows per second is just north of .5 million rows per second. 

Your milage will obviously vary based on row width, disk configuration, etc., but the expectation would be that the load rate is stable over a very wide range of cardinalities. 

Just a quick graphical presentation of the load rate with InfiniDB importing 23.9 billion rows in about 12 1/2 hours.  Rows per second is just north of .5 million rows per second. 

Your milage will obviously vary based on row width, disk configuration, etc., but the expectation would be that the load rate is stable over a very wide range of cardinalities. 

Thanks to all who showed up at the North Texas MySQL Users Group Meeting on Monday night. We had two speakers, Pizza, and beer.

Benjamin Wood talked on the latest news on MySQL products and Robin Schumacher from Calpont discussed building high performance analytic databases.

And Basil won the drawing for the Amazon Kindle!


See you at the next meeting January 4th!

DRBD has entered a new phase. After being developed out of tree for 9 years, and after an extended review and streamlining phase since March, Phil submitted DRBD to be merged into 2.6.32 release of the Linux mainline kernel. The submission was accepted by block layer maintainer Jens Axboe, who merged DRBD in September, then deferred to the 2.6.33 merge window, and this morning Linus …

Just got the following in my email this morning. I sure wish they had done this earlier. “Free Inbound Data Transfer (until June 30, 2010) Data Transfer into AWS will be free of charge from now through June 30, 2010, making it even easier for customers to get their data into AWS. This applies to [...]

There’s one stage in InnoDB crash recovery where it reads log file, you know, this one:

InnoDB: Doing recovery: scanned up to log sequence number 354164119040
InnoDB: Doing recovery: scanned up to log sequence number 354169361920

On a machine with bigger logs it will start spending nearly 100% CPU somewhere in recv_scan_log_recs. Guess what it does…. -fno-inline builds to the rescue:

#0  mem_block_get_len at ./include/mem0mem.ic:86
#1  mem_heap_get_size at ./include/mem0mem.ic:591
#2  recv_scan_log_recs at log/log0recv.c:2727

And:

samples  %        symbol name
8467     72.9222  mem_heap_get_size
291       2.5062  recv_add_to_hash_table
95        0.8182  mem_block_get_len

To speak in layman’s terms, InnoDB does SUM(LENGTH(allocation)) on its relatively wide memory (tens, hundreds of thousands of entries) arena, FOR EVERY LOG SEGMENT, to make sure it didn’t run out of available …