Am 01.01.2014 17:42, schrieb Aleksandr Dezhin: > As you mentioned earlier, max_db_connections can be a source of problems, I > tried to use the default value, but it > did not change the situation. Maybe our database is too slow, but there's > nothing we can do about it. It is quite > big, it is about 100 GB
RAM, RAM and again RAM you need at least the summary of all indexes + 50% on InnoDB perfect would be the whole database size, but in case of dbmail that's not entirely true because there are many many old messages which are not loaded that much rule of thumbs is the innodb_buffer_pool should hold all regulary accessed data and have enough free space for regular operations _____________________________________________ what version of MySQL? starting with 5.5 there are some new config options one of them is "innodb_buffer_pool_instances" which should be innodb_buffer_pool_size in MB / 1024 below our current settings and they improved the performance after upgrade to 5.5 noticeable CAUTION: do not change "innodb_log_file_size" before reading manuals careful! CAUTION: "innodb_file_per_table" is needed for compressed tables (barracuda) but hard to change after tables are created innodb_buffer_pool_size = 5120M innodb_buffer_pool_instances = 5 innodb_purge_threads = 1 innodb_max_purge_lag = 200000 innodb_max_dirty_pages_pct = 60 innodb_additional_mem_pool_size = 32M innodb_log_file_size = 512M innodb_log_buffer_size = 256M innodb_thread_concurrency = 0 innodb_thread_sleep_delay = 10 innodb_flush_log_at_trx_commit = 2 innodb_support_xa = 1 innodb_lock_wait_timeout = 50 innodb_table_locks = 0 innodb_file_format = barracuda innodb_file_per_table = 1 innodb_read_io_threads = 4 innodb_write_io_threads = 4 innodb_doublewrite = 1
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
