does make sense to tune innodb_data_file_path if innodb_file_per_table is active?

Hello guys,

we recently switched all our tables to InnoDB.

I followed the basic instructions at http://bit.ly/3pqQc (mysqlperformanceblog) for the settings.

our server has:

  • 600gb RAID1 15k disk
  • 2 * quad core
  • 24gb of RAM

and this is my InnoDB configuration

-------------------------------------------------------------------------------# ++++ InnoDB Parameters# -------------------------------------------------------------------------------# Generalinnodb_data_home_dir = /var/lib/mysql/innodbinnodb_log_group_home_dir = /var/lib/mysql/innodb/logsinnodb_file_per_tableinnodb_data_file_path = ibdata1:100M:autoextendinnodb_status_file = ib_statusinnodb_autoextend_increment = 10Minnodb_support_xa = 0innodb_thread_concurrency = 8innodb_flush_method = O_DIRECTinnodb_flush_log_at_trx_commit = 2# Memoryinnodb_buffer_pool_size = 16Ginnodb_additional_mem_pool_size = 8Minnodb_open_files = 512# Logginginnodb_log_buffer_size = 8Minnodb_log_file_size = 256Minnodb_log_files_in_group = 2

the only parameter I’m not sure about is
innodb_data_file_path = ibdata1:100M:autoextend

but does it make sense to change that value given I have set innodb_file_per_table on where each table will have it own tablespace?

thank you

if you have innodb_file_per_table on then changing value for parameter innodb_data_file_path doesnt make any sense.

this parameter have significance only have you have single data file.

Not exactly; read http://www.mysqlperformanceblog.com/2010/06/10/reasons-for-r un-away-main-innodb-tablespace/