In a follow-up experiment to an earlier post on TokuDB recovery times, I tried to create a better apples-to-apples comparison to InnoDB recovery time. If I measure recovery times when both DBs are doing the same amount of work, TokuDB requires only 2s to recover from a crash, compared to 1020s for InnoDB.
Background
In the [...]
We recently made transactions in TokuDB 3.0 durable. We write table changes into a log file so that in the event of a crash, the table changes up to the last checkpoint can be replayed. Durability requires the log file to be fsync’ed when a transaction is committed. Unfortunately, fsync’s are not [...]
Last week Tokutek released version 3.0.0 of TokuDB, adding ACID transactions to its list of features. This post discusses an experiment we ran to measure recovery time following a system crash.
In summary, while actively inserting records into a MySQL database using iiBench, we compared the time to recover from a power-cord pull for both [...]
Tokutek is pleased to announce the beta launch of TokuDB for MySQL, version 3.0. Many of our customers have asked for transaction capabilities to provide the data integrity their businesses require and in this release we provide:
Full support for ACID compliant transactions
Fast recovery time (seconds or minutes, not hours or days)
As with previous versions, v3.0 Beta [...]
Last spring, we added a feature that allows the user to see the progress of writes in a statement. Vadim liked it. In 2.2.0, in “show processlist”, we add progress information on reads.
Here is an example of what “show processlist” displays on an update:
mysql> show processlist \G
*************************** 1. row ***************************
Id: 1
User: root
Host: localhost
db: test
Command: Query
Time: [...]
KAYAK, the world’s leading travel search engine, is using TokuDB for MySQL to provide a more personalized user experience. Read all about it in today’s press release.
Tokutek is pleased to announce the general availability of TokuDB for MySQL, version 2.2.0.
At Tokutek, Rich Prohaska used Gearman to automate our nightly build and test process for TokuDB for MySQL. Rich is busy working on TokuDB, so I’m writing up an overview of the build and test architecture on his behalf.
Build and Test Process
Rich created a script, nightly.bash, that gets kicked off every night as a [...]
We often hear from customers and MySQL experts that fragmentation causes problems such as wasting disk space, increasing backup times, and degrading performance. Typical remedies include periodic “optimize table” or dump and re-load (for example, see Project Golden Gate). Unfortunately, these techniques impact database availability and/or require additional administrative cost and complexity. [...]
