When innodb_buffer_pool_load_at_startup is ON, with a large innodb_buffer_pool_size the time to load the buffer pool is very long.
For example with innodb_buffer_pool_size = 378G it took 6.5 hours to load the buffer pool.
I understand that this feature is intended to load it in the background without affecting as much as possible the server performances, but for many high traffic production environments the server cannot be re-pooled into production without a reloaded buffer pool anyway.
It could be very useful in my opinion to have an option, or to modify innodb_buffer_pool_load_at_startup from boolean to multivalue, to force an aggressive load of the buffer pool using a good part of the available resources.
The most flexible implementation of this feature should allow to modify at runtime this value so that if buffer pool load is in progress it will allow to modify it's behaviour between the current one and the aggressive one.
This feature will allow to reduce a lot the time a server has to be taken out of production for maintenance on any heavy traffic environments where modern hardware with large memories is in use.