Databases
StackOverflow2013
Postsdbo
POIs it fit using TokuDB engine when the record average length is 3k?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it fit using TokuDB engine when the record average length is 3k?
    primarykey
    data
    text
    <p>The table have two fields: id, content, and only one Primary key(id).</p> <p>The field id type is bigint. The field content type is TEXT, for this field is var-lenth, maybe some record will be 20k, and average length of record is 3k.</p> <p>Table schema:</p> <pre><code>CREATE TABLE `events` ( `eventId` bigint(20) NOT NULL DEFAULT '0', `content` text, PRIMARY KEY (`eventId`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; </code></pre> <p>It's just used as a Key-Value storage.</p> <p>My Test result is:</p> <pre><code>InnoDB: 2200 records/second TokuDB: 1300 records/second BDB-JE: 12000 records/second LevelDB-JNI: 22000 records/second(not stable, need test again) </code></pre> <p>the result is very very bad. </p> <p>Is 3K too big for tokuDB?</p> <p>In My Application, there many insert(>2000 records/second， about 100M records/day), and rare update/delete. </p> <pre><code>TokuDB version: mysql-5.1.52-tokudb-5.0.6-36394-linux-x86_64-glibc23.tar.gz InnoDB version: mysql 5.1.34 OS: CentOS 5.4 x86_64 </code></pre> <p>One reason that we choose InnoDB/TokuDB is we need partition support and maintenance friendly. Maybe I will try LevelDB or other Key-Value storage? any sugguest will welcome.</p> <p>===========</p> <p>Thanks everybody, finally test performance of TokuDB and InnoDB both not good enough for our use case.</p> <p>Now we have using solution like bitcask as our storage. Bitcask append-only style write performance is much better than what we expect. We just need to handle the memory problem about the hash index.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBen
    1. USBen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs it fit using TokuDB engine when the record average length is 3k?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo why not just use InnoDB?
      singulars
      1. POIs it fit using TokuDB engine when the record average length is 3k?
      1. USChris Bornhoft
    2. COWe expect the performance to be >5000 records/second, and we data are append-only style.
      singulars
      1. POIs it fit using TokuDB engine when the record average length is 3k?
      1. USBen
    3. COAnd what version of MySQL are you using? InnoDB has been greatly improved from 5.5 and on. It can easily handle that kind of load when correctly configured. Row-level locks will help with clogging as well.
      singulars
      1. POIs it fit using TokuDB engine when the record average length is 3k?
      1. USChris Bornhoft
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload