Oracle 5.0 Reference Manual page 1250

innodb_log_group_home_dir = /dr3/iblogs
#
# Set the log file size to about 25% of the buffer pool size
innodb_log_file_size=250M
innodb_log_buffer_size=8M
#
innodb_flush_log_at_trx_commit=1
innodb_lock_wait_timeout=50
#
# Uncomment the next line if you want to use it
#innodb_thread_concurrency=5
In some cases, database performance improves if the data is not all placed on the same physical disk.
Putting log files on a different disk from data is very often beneficial for performance. The example
illustrates how to do this. It places the two data files on different disks and places the log files on the
third disk.
InnoDB
partitions (raw devices) as
Raw Devices for the Shared
Tuning other
[mysqld]
skip-external-locking
max_connections=200
read_buffer_size=1M
sort_buffer_size=1M
#
# Set key_buffer to 5 - 50% of your RAM depending on how much
# you use MyISAM tables, but keep key_buffer_size + InnoDB
# buffer pool size < 80% of your RAM
key_buffer_size=value
On Linux, if the kernel is enabled for large page support,
memory for its buffer pool and additional memory pool. See
Support".
14.2.1.1. Using Per-Table Tablespaces
You can store each
tablespaces" because in effect each table has its own tablespace.
Using multiple tablespaces can be beneficial to users who want to move specific tables to separate
physical disks or who wish to restore backups of single tables quickly without interrupting the use of
other
InnoDB
InnoDB
fills the tablespace beginning with the first data file. You can also use raw disk
data files, which may speed up I/O. See
InnoDB
Tablespace".
Warning
On 32-bit GNU/Linux x86, you must be careful not to set memory usage too
high. may permit the process heap to grow over thread stacks, which
glibc
crashes your server. It is a risk if the value of the following expression is close to
or exceeds 2GB:
innodb_buffer_pool_size
+ key_buffer_size
+ max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size)
+ max_connections*2MB
Each thread uses a stack (often 2MB, but only 256KB in MySQL binaries
provided by Oracle Corporation.) and in the worst case also uses
sort_buffer_size + read_buffer_size
By compiling MySQL yourself, you can use up to 64GB of
physical memory in 32-bit Windows. See the description for
innodb_buffer_pool_awe_mem_mb
Startup Options and System
server parameters. The following values are typical and suit most users:
mysqld
table and its indexes in its own file. This feature is called "multiple
InnoDB
tables.
Configuration
[1238] in
Variables".
can use large pages to allocate
InnoDB
Section 8.9.7, "Enabling Large Page
1230
Section 14.2.1.2, "Using
additional memory.
Section 14.2.2, "InnoDB