InnoDB performance tuning tips.
PRIMARY KEY wastes a lot of disk space because its value must be stored with every secondary index record.
AUTO_INCREMENT column as the primary key if the primary key is long.
top shows the CPU usage percentage is less than 70%, the workload is probably disk-bound.
InnoDB must flush the log to disk at each transaction commit if that transaction made modifications tothe database.
InnoDB has written the log files full, it
has to write the modified contents of the buffer pool to disk
in a checkpoint.
VARCHAR data type instead of CHAR if storing variable-length strings or if the column may contain many NULL values.
CHAR(N) column always takes N characters to store data, even if the string is shorter or its value is NULL.
Are there any more performance tuning tips?
© 2007 John Michael Pierobon