Today found a backup of the MySQL Data folder is unusually large, a discovery is more than three files: ibdata1 Ib_logfile0 Ib_logfile1, the former 18m, after the two 5m, The original migration from the mysql5.0 to 5.5, and 5.5 off InnoDB start up, so I opened the InnoDB, because InnoDB will increase the default number of these data files and log files, resulting in large. Try to set the size of the data file, the result tells me the minimum 10m, or too large, and then explore the way to close the InnoDB.
See the log found that because of the MySQL program upgrade, need to run Mysql_upgrade upgrade MySQL inside the database, this relatively simple, and MySQL command usage is the same, run it again OK. Then found that still can't close innodb, very strange, check the original mysql5.5 default use InnoDB, so can not simply close off, but also to set the default engine for MyISAM can, in the MY.CNF add the following two sentences:
Copy Code code as follows:
Default-storage-engine=myisam
Innodb=off
Restart MySQL, and then delete the three annoying files.
MySQL 5.6 Disable InnoDB
InnoDB is a MySQL developed after the Oracle acquisition, support transactions and row-level locks and other advanced features, but not everyone needs innodb, for most people, the previous MyISAM engine is enough, generally choose to change the default engine to MyISAM, But InnoDB still consumes memory and hard drives, and then you need to disable InnoDB completely.
In the previous MySQL, the general can be so set on the line:
Copy Code code as follows:
Default-storage-engine=myisam
Skip-innodb
However, in the latest MySQL5.6, this setting is not able to start, you need to add a set:
Copy Code code as follows:
Default-tmp-storage-engine=myisam
Not only that, you need to add the following configuration, otherwise the program will easily exit:
Copy Code code as follows:
Loose-innodb-trx=0
Loose-innodb-locks=0
Loose-innodb-lock-waits=0
Loose-innodb-cmp=0
Loose-innodb-cmp-per-index=0
Loose-innodb-cmp-per-index-reset=0
Loose-innodb-cmp-reset=0
Loose-innodb-cmpmem=0
Loose-innodb-cmpmem-reset=0
Loose-innodb-buffer-page=0
Loose-innodb-buffer-page-lru=0
Loose-innodb-buffer-pool-stats=0
Loose-innodb-metrics=0
Loose-innodb-ft-default-stopword=0
Loose-innodb-ft-inserted=0
Loose-innodb-ft-deleted=0
Loose-innodb-ft-being-deleted=0
Loose-innodb-ft-config=0
Loose-innodb-ft-index-cache=0
Loose-innodb-ft-index-table=0
Loose-innodb-sys-tables=0
Loose-innodb-sys-tablestats=0
Loose-innodb-sys-indexes=0
Loose-innodb-sys-columns=0
Loose-innodb-sys-fields=0
Loose-innodb-sys-foreign=0
Loose-innodb-sys-foreign-cols=0
Excerpt from http://docs.oracle.com/cd/E17952_01/refman-5.6-en/innodb-turning-off.html
In addition, MySQL 5.6:5.5 occupies more physical memory, virtual memory and 5.5 use almost (5.5 is also a large virtual memory consumer). Performance increased by about 30% per cent (according to official documents, without specific tests). 5.5.
