To describe the phenomenon, my program is on the data from the terminal, the insert to mysql table,
Use found in the process, always after a period of time (hours), will appear the insert operations, and duration ranging from 5 to 20 seconds, but then returned to normal,

After continuous exploration and found the mysqld. Exe footprint will continue to rise, and rise to a certain degree, it is no longer increases, the rise is about the size of the innodb_buffer_pool_size, and Innodb_buffer_pool_pages_free this value was running out of time, is mysql statement hang, hang the amount of time, typically several seconds,

I tried to modify the innodb_buffer_pool_size this value, but because of Innodb_buffer_pool_pages_data will increase constantly, again big innodb_buffer_pool_size also of no help,

Ask how to avoid this kind of Innodb_buffer_pool_pages_free deplete the mysql hang? What exactly is this principle, I probably guess should be mysql to switch between the memory and disk, but really can't receive the hang time, although it is a one-off,

CodePudding user response:

Mysql data regularly from memory flush to disk file, this will take time, unless large enough memory

CodePudding user response:

reference 1st floor oyljerry response:

mysql data regularly from memory flush to disk file, this will take time, unless large enough memory

Thank moderator greatly, want to know about the rules of the flush to disk file memory might be, cycle is long, every time need time and what relevant again,
Whether innodb_buffer_pool_size used after will flush time,

Thanks again,
I've probably know what to do, I'm going to clear data on a regular basis, control the amount of data within the scope of the innodb_buffer_pool_size,

CodePudding user response:

How big is your inner, I estimate is too large innodb_buffer_pool_size configuration

CodePudding user response:

What is the backup work in a lock table then?