InnoDB Buffer Pool memory growth during write-heavy workloads

MySQL InnoDB manages memory via the buffer pool to cache data and index pages. While memory usage typically stabilizes at the innodb_buffer_pool_size limit, certain internal structures such as the adaptive hash index and the change buffer contribute to the overall memory footprint.

Under sustained write-heavy workloads, the adaptive flushing algorithm adjusts the rate at which dirty pages are written to disk based on redo log generation. There is uncertainty regarding whether specific memory growth observed during these periods is a result of internal allocation for these auxiliary structures or a failure of the flushing mechanism to keep pace with page dirtiness, potentially leading to checkpoint stalls.

• Does the performance_schema.memory_summary_global_by_event_name table capture all allocations related to the adaptive hash index during peak write activity?
• How does the interaction between innodb_adaptive_flushing and the buffer pool's internal memory accounting affect reported memory usage in MySQL 8.0?