Tokutek Fractal Tree indexes
What Fractal Tree / TokuDB claimed for ingest — and how to evaluate any engine.
Tokutek’s Fractal Tree indexes (TokuDB) targeted sustained ingest with large indexes: message buffering in the tree to reduce random IO, compression as a first-class feature.
Evaluate like an operator
- Sustained insert after the working set exceeds RAM
- Range-scan latency under compression
- Backup, replication, crash recovery, online DDL
- Vendor/community trajectory
Takeaway
Serious idea; useful competitive pressure. Many estates still chose InnoDB for operational familiarity. Keep exotic engines when your soak tests show a clear ingest win and you can restore at 03:00.
The engine you cannot recover is not “faster.”