The Ubuntu Developer Summit takes place at The Oakland Marriott City Center, Oakland, California from 7–11 May 2012. 

If your attending this event, you will have a few different MySQL opportunities to attend:

• MySQL RoundTable
• Utilities to work with MySQL
  

Oracle is proud to also be a Sponsor of the Ubuntu Developer Summit. A full schedule of the event is available here.

 Join us as we help support and grow the MySQL Communities. 

FYI: A MySQL Optimizer Team blog aggregate page has been launched. It will be continuously updated with the latest blogs published by the MySQL optimizer developers. Now you can easily stay updated ;-)

It's now over a year when there was a quite interesting exchange with Vadim and other Percona guys due their TPCC-like benchmark results on MySQL 5.5 - I've replayed on that time the same tests, but with a better tuned configuration parameters to demonstrate that with a little bit more love, MySQL 5.5 may keep TPCC-like workload very well ;-)) However, it was clear that Adaptive Flushing in 5.5 needs some improvement (which is now implemented in 5.6), but there were also several open questions regarding I/O level and …

I have been a fan of LINQ for several years (my Saffron project covered many of the same themes) but I've had difficulty explaining why it isn't just a better Hibernate. In his article “Why LINQ Matters: Cloud Composability Guaranteed” (initially in ACM Queue, now in April's CACM), Brian Beckman puts his finger on it.

The idea is composability.

He writes:
Encoding and transmitting such trees of operators across tiers of a distributed system have many specific benefits, most notably:

Download PDF Presentation

While MySQL is a popular and widely used database product, there are some default features and settings which can be foreign in comparison with other commercial RDBMS products such as Oracle. In this discussion, Ronald Bradford will discuss some of the MySQL defaults that are not what you may expect. These include understanding the concept of storage engines, and the default non-transactional state, how silent data truncations occur which affect your data, ideal practices for date management, and the MySQL transaction isolation options. These are all critical to clearly understand and implement correctly for data integrity and consistency. He will cover in-depth topics including SQL_MODE and the recommended best …

Note: this article was originally published on http://blogs.innodb.com on April 13, 2012 by Inaam Rana.

In MySQL labs release April 2012 we have reworked the flushing heuristics in InnoDB. In this post I’ll give an overview of what we have changed and the various configuration variables we have introduced to fine tune the flushing algorithm. If you are interested in finding out how our new flushing algorithm fares in benchmarks you can get these details in Dimitri’s well-explained blog here.

Flushing means writing dirty pages to disk. I have explained in some detail about adaptive_flushing and …

In MySQL labs release April 2012 we have reworked the flushing heuristics in InnoDB. In this post I’ll give an overview of what we have changed and the various configuration variables we have introduced to fine tune the flushing algorithm. If you are interested in finding out how our new flushing algorithm fares in benchmarks you can get these details in Dimitri’s well-explained blog here.

Flushing means writing dirty pages to disk. I have explained in some detail about adaptive_flushing and types of flushing in my previous notes. Please go through these notes if you want to …

Collaborate is April 22-26
at the Mandalay Bay Convention Center
in Las Vegas. Below is a list of the MySQL sessions. And besure to stop by the Demo area to see some new MySQL goodies!

The MySQL Community Team won a MySQL Community Awards: Corporate Contributor award. On behalf my fellow MySQL Community Manager Keith Larson and myself, we would like to thank those who apprecaited our efforts. But it is not just Keith and I — we have a strong team that is achored by amazing developers, marketeers, salespersons, managers, engineers of several varieties, and many more hard working folks who regularly make us look good. Lots of hard work of folks you do not see at conferences go into making being on the MySQL Community Team look good.

With this award the panel wishes to acknowledge the Oracle MySQL Community team especially for the free tech tours and developer workshops they arrange around the world and their participation at conferences of many kinds. This MySQL evangelization reaches a unique audience, many of …

Checkpointing — which involves periodically writing out dirty pages from memory — is central to the design of crash recovery for both TokuDB and InnoDB. A key issue in designing a checkpointing system is how often to checkpoint, and TokuDB takes a very different approach from InnoDB. How often and how much InnoDB checkpoints is complicated, but under certain workloads it can be relatively infrequent. In contrast, TokuDB runs a complete checkpoint starting one minute after the last one ended.

Frequent checkpoints make for fast recovery. Once MySQL crashes, the storage engine needs to replay the log to get back to a correct state. The length of the log is a function of the time since the last checkpoint for TokuDB and a more complicated function of the workload for InnoDB. And replaying the log is single threaded. So TokuDB recovers in minutes, and …