If you read my post on Drizzle transaction message limits, you know that it is possible to have multiple Transaction protobuf messages (segments) for a single database transaction. This was necessary to keep the Google protobuf messages from growing too large (there is a maximum limit on message size). Before my most recent change, you [...] [...more]
Sam Rash from Facebook came by and talked to us about the how they provide near-realtime access to data logged from Scribe into HDFS. Very fascinating. Enjoy! Low Latency Message Bus with Scribe and HDFS Sam Rash (Facebook) Tuesday, August 31, 2010 ABSTRACT This talk covers the Data Freeway project at Facebook, which centers around [...] [...more]
… and really testing the replication code path for CREATE TABLE. So, for a very long time now, Drizzle has been using a protobuf based structure to describe the structure of tables. The idea was to be able to have engines rather painlessly generate this structure themselves (which several now do). A secondary idea was [...] [...more]
Some recent changes I made have recently been pushed to Drizzle trunk that affect the size of the Transaction protobuf message that any replication stream will see (e.g., the transaction log). This was necessary to fix bug 600795. Without a Transaction message size limit, for any bulk operations, like LOAD DATA, we would have ended [...] [...more]
If you read Percona’s whitepaper on Goal-Driven Performance Optimization, you will notice that we define performance using the combination of three separate terms. You really want to read the paper, but let me summarize it here: Response Time – This is the time required to complete a desired task. Throughput – Throughput is measured in [...] [...more]
