How are InnoDB in memory structures handled in MySQL?
InnoDB In-Memory Structures Buffer Pool Change Buffer Adaptive Hash Index Log Buffer InnoDB On-Disk Structures Tables Creating InnoDB Tables Creating Tables Externally Importing InnoDB Tables Moving or Copying InnoDB Tables Converting Tables from MyISAM to InnoDB AUTO_INCREMENT Handling in InnoDB Indexes
What should MySQL cache size be for 8GB RAM?
That would be 62.5% of RAM with a sufficient amount of RAM for the Server OS plus memory for DB Connections @kvisle recommended using mysqltuner.pl. That script is excellent for judging the amount of RAM to dedicate to join_buffer_size, sort_buffer_size, read_buffer_size, and read_rnd_buffer_size.
What do you need to know about InnoDB tables?
MySQL Programs MySQL Server Administration Security Backup and Recovery Optimization Language Structure Character Sets, Collations, Unicode Data Types Functions and Operators SQL Statements MySQL Data Dictionary The InnoDB Storage Engine Introduction to InnoDB Benefits of Using InnoDB Tables Best Practices for InnoDB Tables
Which is the default storage engine for MySQL?
SQL Statements MySQL Data Dictionary The InnoDB Storage Engine Introduction to InnoDB Benefits of Using InnoDB Tables Best Practices for InnoDB Tables Verifying that InnoDB is the Default Storage Engine Testing and Benchmarking with InnoDB
Why does InnoDB not release disk space after deleting data?
Ever. Even if you use optimize table to free the space used from deleted records, it will reuse it later. An alternative is to configure the server to use innodb_file_per_table, but this will require a backup, drop database and restore. The positive side is that the .ibd file for the table is reduced after an optimize table.
Why does MySQL not release disk space after deleting data?
What happens is, that even if you drop the database, innodb will still not release disk space. I had to export, stop mysql, remove the files manually, start mysql, create database and users, and then import. Thank god I only had 200MB worth of rows, but it spared 250GB of innodb file. Fail by design.