Preload table / index into buffer_pool

Registered by Evgeniy Stepchenko on 2009-04-08

Preload table / index into buffer_pool. You can use custom queries by primary / secondary key to “warm up” part of table, but this solution is ugly and may be slow due to random logical I/O. Implementing preload of full .ibd file with sequential read would be much better solution. This is actually more important feature than it may appear at first look - for example if you put load on slave which is not warmed up properly - slave may never catch up slave, but with small load warm up may take hours to complete, so basically it adds several hours for operations team to complete task which requires restart of slave

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Sprints

Whiteboard

port to the patches too

Note: The 'ugly' preloading of writing a .sql file to index/tablescan doesn't work as well any more either. InnoDB plugin modified it's page replacement algorithm to have table scan prevention.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.