Hi,
Currently I'm trying to tune innodb_buffer_pool_size.
That in itself seems ok based on the guidelines provided.
In the InnoDB engine, is max_heap_table_size taken into account?
I have some big tables ( ie. ranging from 1G to 6G currently)
If the max_heap_table_size is low ( say 64M for example), will the vast majority of these tables require intensive disk IO?
I have a powerful server with ~100G physical RAM.
So looking at a pool allocation of about 85G.
The over all table data size is currently about 30G but expected to grow somewhat.
Can I set the max_heap_table_size to be ~6G?
In theory this should allow all these large tables to be cached - is this correct?
Is there anything else to be considered?
Any negatives in relation to this configuration?
Appreciate any thoughts.
Thanks.
Currently I'm trying to tune innodb_buffer_pool_size.
That in itself seems ok based on the guidelines provided.
In the InnoDB engine, is max_heap_table_size taken into account?
I have some big tables ( ie. ranging from 1G to 6G currently)
If the max_heap_table_size is low ( say 64M for example), will the vast majority of these tables require intensive disk IO?
I have a powerful server with ~100G physical RAM.
So looking at a pool allocation of about 85G.
The over all table data size is currently about 30G but expected to grow somewhat.
Can I set the max_heap_table_size to be ~6G?
In theory this should allow all these large tables to be cached - is this correct?
Is there anything else to be considered?
Any negatives in relation to this configuration?
Appreciate any thoughts.
Thanks.