This comment is in regard to this InnoDB blog page. Trying to post a
message says you need to be logged in, but there’s no
register/login page I could see…

Anyway the page talks about a new feature which allows you to
save on shutdown an InnoDB buffer pool and to load this on
startup, this ensuring that once loaded the database will perform
with this “hot” cache.

That sounds interesting as I have seen on numerous occasions that
if the buffer pool is not warm then performance can be a
magnitude worse.

This looks like a very welcome feature. However, a couple of
things are not clear to me.

Having some example benchmark times of using this process and
comparing it to trying to warm up the buffer pool by hand would
be useful. While this may heavily dependent on database …

The following quirky dynamic SQL will scan each index of each
table so that they’re loaded into the key_buffer (MyISAM) or
innodb_buffer_pool (InnoDB). If you also use the PBXT engine
which does have a row cache but no clustered primary key, you
could also incorporate some full table scans.

To make mysqld execute this on startup, create
/var/lib/mysql/initfile.sql and make it be owned by mysql:mysql

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.