Hi, > innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend > innodb_buffer_pool_size = 6G
it looks like your InnoDB tablespace is less than 2G. If it is true then IMHO it doesn't make any sense to allocate 6G for innodb_buffer_pool. InnoDB won't use it. Best regards, Mikhail. ----- Original Message ----- From: "nm" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 30, 2003 10:17 AM Subject: guru needed - large configuration MySQL-Max InnoDB - 4.0.16 > > Hi there > > I was wondering I you can send your comments and remarks for this my.cnf > file > > ---- > o.s. redhat9 > tables < 20Mb > mem: 8gb > server dedicated to mysql > max_connections=2000/3000 > uses only innodb tables > ---- > > --------my.cnf > [mysqld] > port = 3306 > socket = /var/lib/mysql/mysql.sock > skip-locking > key_buffer = 384M > max_allowed_packet = 1M > table_cache = 512 > sort_buffer_size = 2M > read_buffer_size = 2M > myisam_sort_buffer_size = 64M > thread_cache = 8 > query_cache_size = 32M > # Try number of CPU's*2 for thread_concurrency > thread_concurrency = 8 > max_connections=2000 > #max_connections=3000 > > > > innodb_data_home_dir = /var/lib/mysql/ > innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend > innodb_log_group_home_dir = /var/lib/mysql/ > innodb_log_arch_dir = /var/lib/mysql/ > > > > innodb_buffer_pool_size = 6G > innodb_additional_mem_pool_size = 20M > > > innodb_log_file_size = 100M > innodb_log_buffer_size = 8M > innodb_flush_log_at_trx_commit = 1 > innodb_lock_wait_timeout = 50 > > > ------ > > I found few documents on mysql tuning. Do you have any suggestions? > Experience? > Thanks. > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
