Shantanu's Blog

Corporate Consultant

October 25, 2013

 

TokuDB an engine of future


TokuDB is highly recommended for slaves in production environment. Here are 9 advantages of using TokuDB in production.

1) Data warehouse / big data solution:
TokuDB may take the same amount of time to complete the query if the data is small and fits in memory.
But with huge data, InnoDB is not able to perform while tokuDB gives you quick results.

2) Integrates with MySQL:
TOkuDB is an engine just like MyISAM and InnoDB. It is listed as default engine in the output of "show engines" command.

3) Highly compressed data:
TokuDB compresses data upto 15 to 20% compared to MyISAM or InnODB.

Tokudb disk consumption:
-rwxrwx--x 1 root root 222M Oct 25 19:27 _akola_ticket_main_41e0_1_18_B_0.tokudb
-rwxrwx--x 1 root root  68M Oct 25 19:27 _akola_ticket_key_tripindex_41e0_1_18_B_2.tokudb
-rwxrwx--x 1 root root  52M Oct 25 19:27 _akola_ticket_key_route_no_41e0_1_18_B_5.tokudb
-rwxrwx--x 1 root root  50M Oct 25 19:27 _akola_ticket_key_adjtripno_41e0_1_18_B_3.tokudb
-rwxrwx--x 1 root root  36M Oct 25 19:42 _akola_ticket_key_wbindex_41e0_1_18_B_1.tokudb
-rwxrwx--x 1 root root  34M Oct 25 19:27 _akola_ticket_key_NewIndex1_41e0_1_18_B_4.tokudb

MyISAM disk consumption for the same table:
-rw-rw---- 1 root root 1.5G Jul 10 00:36 ticket.MYD
-rw-rw---- 1 root root 335M Jul 10 00:40 ticket.MYI

4) Easily transfer data:
I can simply alter table to toku using alter table statement.

alter table tbl_name engine=TokuDB;

Or I can take the backup without specifing the engine. Since TokuDB is the default engine, it will be converted to tokudb while restoring data.

mysqldump db_name --routines --compatible=no_table_options > db_name_to_toku.sql

5) Crash Revoery:
TOkuDB has one of the excellent crash recovery feature just like InnoDB (that MyISAM is missing!)

6) Replication — Eliminate Slave Lag:
MySQL’s single threaded design often leads to slave lag. With TokuDB, slave lag is eliminated.
This insures replication can be used for read scaling, backups, and disaster recovery, without resorting to sharding, expensive hardware.

7) Hot Schema Changes in Seconds:
TokuDB introduced Hot Column Addition (HCAD). You can add or delete columns from an existing table with minimal downtime.

8) No need to configure parameters:
You may need to increase only open files limit if you get an error something like...
[ERROR] Error in accept: Too many open files
open-files-limit=40000

Other than this you do not need to configure anything! Now compare this with InnoDB.

By default, TokuDB uses about half the memory of the machine as buffer pool (or disk cache). That leaves the other half of memory for the OS to allocate.

9) InnoDB disk consumption:
InnoDB stores data in ibdata files and the disk consumption is not reduced even if you drop tables.
TokuDB tables works like MyISAM and frees the disk space immediately once you drop / truncate tables.

Labels: , ,


Comments: Post a Comment

<< Home

Archives

June 2001   July 2001   January 2003   May 2003   September 2003   October 2003   December 2003   January 2004   February 2004   March 2004   April 2004   May 2004   June 2004   July 2004   August 2004   September 2004   October 2004   November 2004   December 2004   January 2005   February 2005   March 2005   April 2005   May 2005   June 2005   July 2005   August 2005   September 2005   October 2005   November 2005   December 2005   January 2006   February 2006   March 2006   April 2006   May 2006   June 2006   July 2006   August 2006   September 2006   October 2006   November 2006   December 2006   January 2007   February 2007   March 2007   April 2007   June 2007   July 2007   August 2007   September 2007   October 2007   November 2007   December 2007   January 2008   February 2008   March 2008   April 2008   July 2008   August 2008   September 2008   October 2008   November 2008   December 2008   January 2009   February 2009   March 2009   April 2009   May 2009   June 2009   July 2009   August 2009   September 2009   October 2009   November 2009   December 2009   January 2010   February 2010   March 2010   April 2010   May 2010   June 2010   July 2010   August 2010   September 2010   October 2010   November 2010   December 2010   January 2011   February 2011   March 2011   April 2011   May 2011   June 2011   July 2011   August 2011   September 2011   October 2011   November 2011   December 2011   January 2012   February 2012   March 2012   April 2012   May 2012   June 2012   July 2012   August 2012   October 2012   November 2012   December 2012   January 2013   February 2013   March 2013   April 2013   May 2013   June 2013   July 2013   September 2013   October 2013   January 2014   March 2014   April 2014   May 2014   July 2014   August 2014   September 2014   October 2014   November 2014   December 2014   January 2015   February 2015   March 2015   April 2015   May 2015   June 2015   July 2015   August 2015   September 2015   January 2016   February 2016   March 2016   April 2016   May 2016   June 2016   July 2016   August 2016   September 2016   October 2016   November 2016   December 2016   January 2017   February 2017   April 2017   May 2017  

This page is powered by Blogger. Isn't yours?