This is what I’m talking about, this is fantastic news! Anxiously looking forward to the WB 6.0 public Beta test phase for Mac / OS X…hopefully soon?

Over several blog posts, Tim has presented performance results on large data sets of TokuMX, our MongoDB product with fractal tree indexes integrated, side by side with MongoDB. Results look good. We’ve shown improved throughput numbers on a sysbench benchmark, faster load times, and high compression.

So what is TokuMX, and how does it achieve this performance?

TokuMX has replaced ALL of the storage code in MongoDB with fractal trees. Every collection, every secondary index, every metadata collection is stored with fractal trees, the same technology that implements the TokuDB storage engine for MySQL. That is, all data is stored and managed with our transactional, ACID and MVCC-compliant, write-optimized storage library.

TokuMX achieves …

On Friday I gave a presentation on “MySQL Query Patterns, Optimized” for Percona MySQL Webinars.  If you missed it, you can still register to view the recording and my slides.

Thanks to everyone who attended, and especially to folks who asked the great questions.  I answered as many as we had time for  during the session, but here are all the questions with my complete answers:

Q: Can you compare the use of subqueries/multiple joins vs. multiple queries (e.g. temp tables)?

For performance, it’s hard to make …

Back in November, I filed MySQL bug 67448, talking about a different type of max_allowed_packet problem.

See, an application had put data into the database, but could not retrieve it without getting max_allowed_packet. With the help of some really smart community folks (named Jesper Hansen, Brandon Johnson and Shane Bester), we determined that MySQL actually has 2 different max_allowed_packet settings: client and server.

When you change the max_allowed_packet variable, you are changing the server variable if it is in [mysqld] and the client variable if it is in [client] or [mysql] or whatever client you have. As far as we can tell, there’s no way to actually view what the client variable is, as looking at both the session and global max_allowed_packet variable shows you the server variable.

If max_allowed_packet is not set by the client, it defaults to …

I have never been to a DrupalCon before so my first was DrupalCon Portland 2013 (with some 3,500+ attendees). My first DrupalCon happened to also be one that I spoke at, and I hope to return to Austin in 2014 (added bonus: I’ve never been to Texas before).

SkySQL had decided to get a booth at DrupalCon since I was speaking and I have to say that the booth was very successful. You may ask why and the simple reasons are:

1. Everyone at DrupalCon was a user of MySQL. Once they hit scale, they may need professional services or even just switch to MariaDB. This is a captive audience.
2. Everyone running Drupal at scale with many modules and nodes generally faced issues with database slowdowns. Hello …

The MySQL for Developers course teaches you the knowledge, skills, tools and issues involved in writing applications with the MySQL database server. It forms the core of the MySQL Developer learning path.

During this 5-day course, you will perform lab work with Java and PHP, connecting to MySQL databases and executing queries and stored routines. Enrolling in this course will simultaneoursly help you prepare for the Oracle Certified Professional, MySQL Developer certification.

You can take this instructor-led course as a:

• Live-virtual event: Take this class live, from your own desk. No travel required. You can choose from a wide selection of events on the schedule to suit different timezones.
• In-class event: …

Hi Daniel,

Thanks for your comment. The function lock_get_mode() is declared as an inline function. Are you using optimized build? Also, in gdb, try the option "/4bt" instead of just "/4t" for the command "x". I think it is better to specify the size of the object explicitly.

Rgds,
anna

In the replication topology I manage there are many layers of replication filters that prune data at the database and in a few places table level. The way MySQL replicates Data Definition Language (create, alter, drop) statements differs from how Data Manipulation Language (insert, update, delete) statements are handled with row-based replication. I often need to fix broken replication due to a lack of understanding of these subtle differences.

With row-based replication DML statements focus directly on the table being modified. DDL on the other hand always uses statement-based replication and is tied to what is known in MySQL as the "default database". The default database is the schema/database currently in use when a DDL …

I really like the article.

I had to use lock_get_mode_str() instead of lock_get_mode(). And the bitmap was printed differently.

(gdb) p $rowlock
$3 = (ib_lock_t *) 0x7f9f94011d40
(gdb) p lock_get_mode($rowlock)
No symbol "lock_get_mode" in current context.
(gdb) p lock_get_mode_str($rowlock)
$4 = 0xc346b8 "X"

(gdb) x /4t $rowlock + 1
0x7f9f94011d88: 00000000000000000000000000011110 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000

This is with 5.6.10 on Linux (64-bit).

And maybe it's better to put the PDF link in at the beginning of the article.

Since Tarantool stored procedure API was extended with socket I/O, a whole universe of applications for data-enriched networking (routing, proxying, PUSH-notifications, and so on) has become possible.

But there is one case which doesn't lend itself so easily: anything MySQL. The first scenario I'd love to support is when Tarantool works as a smart write-back cache for MySQL, providing a higher update RPS, but automatically maintaining a slightly dated copy of all the data in a relational database.

One dramatic shortcoming of MySQL universe, which, IMHO, if addressed properly, could spark a whole new set of uses and third-party solutions, is the clumsiness of the client-server protocol.

The MySQL client-server protocol is unnecessarily hard to implement: it is built on top of a layered design, with built-in compression and transport-level tricks to be able to communicate over unreliable protocol such as …