This repository has been archived by the owner on Jun 12, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
Testing TokuDB
Rik Prohaska edited this page May 29, 2015
·
24 revisions
- Run fractal tree unit tests
- Duration: 20 minutes on a 16 core machine
- Duration with valgrind: 4 hours on a 16 core machine
The fractal tree unit tests with code coverage ON should be run on the TokuDB and TokuMX release branches. This is NOT currently done.
- Run fractal tree stress tests
- Duration: currently unlimited
- Run TokuDB MySQL tests
- Duration: 3 hours on an 8 core machine
- Duration with valgrind: 4 hours on an 8 core machine
- Run sql bench tests with TokuDB
- Duration: about 2.5 hours
- Run the TokuDB storage engine unit tests
- Duration: 8 hours
This test loads a TPC-H database with a given scale factor into TokuDB and verifies that the data is correct by comparing with a good copy of the data. The test also verifies that fractal trees by running 'check table' on the various TokuDB tables.
- Load various TPC-H databases with data and table verification
- Duration 1G: 5 minutes
- Duration 10G: 39 minutes
- Duration 30G: 2 hours
- Duration 100G: unknown
- Air traffic ontime tests
- Duration: 1.5 hours
The iibench test writes rows to a table with an auto increment primary key and 3 secondary keys with concurrent queries to the table. When 1B rows are written, the fractal trees for the table are verified with 'check table'.
- Run iibench script
- Duration: 24 hours on a big machine
- What are the benchmarks?
- How are the benchmark results analyzed?
- Where are the test scripts?
- What is the test duration?
- Run the hot backup unit tests
- Duration: 49 seconds
- Duration with valgrind: 17 seconds
- Where are the tests scripts?
- What is the test duration?
- Testing read free replication
- No scripts available
- Duration unknown
- What tests are run?
- Where are the test scripts?
- What is the test duration?