![]() ![]() The main drawback of high values for max_connections (like 1000 or more) is that the server will become unresponsive if for any reason it has to run 1000 or more active transactions. It is very frequent that because the application does not close connections to the database correctly, you need much more than the default 151 connections. Max_connections: if you are often facing the ‘Too many connections’ error, max_connections is too low. If you know your application is write-intensive and you are using MySQL 5.6, you can start with innodb_log_file_size = 4G. Starting with innodb_log_file_size = 512M (giving 1GB of redo logs) should give you plenty of room for writes. ![]() Until MySQL 5.5 the total redo log size was limited to 4GB (the default is to have 2 log files). Fortunately, crash recovery performance has improved a lot since MySQL 5.5 so you can now have good write performance and fast crash recovery. Up to MySQL 5.1, it was hard to adjust, as you wanted both large redo logs for good performance and small redo logs for fast crash recovery. The redo logs are used to make sure writes are fast and durable and also during crash recovery. Innodb_log_file_size: this is the size of the redo logs. The buffer pool is where data and indexes are cached: having it as large as possible will ensure you use memory and not disks for most read operations. Innodb_buffer_pool_size: this is the #1 setting to look at for any installation using InnoDB. If you do not, you are very likely to run into problems very quickly. Here are 3 MySQL performance tuning settings that you should always look at.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |