TokuDB gotchas: slow INFORMATION_SCHEMA TABLES_MySQL
We are usingPercona Server + TokuDB engineextensively inPercona Cloud Toolsand getting real usage operational experience with this engine. So I want to share some findings we came across, in hope it may help someone in their work with TokuDB. So, one problem I faced is that select * from information_schema.tables limit 1000;...1000 rows in set (18 min 31.93 sec)
This is very similar to what InnoDB faced a couple years back. InnoDB solved it by addingvariable So what happens with TokuDB? There is an explanation from Rich Prohaska at Tokutek: “Tokudb has too much overhead for table opens. TokuDB does a calculation on the table when it is opened to see if it is empty. This calculation can be disabled when ‘ So let’s see what we have with select * from information_schema.tables limit 1000;...1000 rows in set (3 min 4.59 sec)
An impressive improvement, but still somewhat slow. Tokutek promises a fix to improve it in the next TokuDB 7.2 release. |