The application is a news website, apart from the standard news insertions to the db, news article read analytics are also recorded to the db. That means one sql entry for each page view (30-50 visits/second). Before all this the db was set to myisam, we were experiencing issues with table crashes so we decided to switch to innodb.
The problem: Since the move, mariadb has started to eat up all the space in /tmp. I don't have /tmp partitioned to a separate partition so it ends up eating all the disk. I've tried looking for something regarding this online but haven't been able to find anything that would help.
CPU consumption stands around 40-50% and overall server ram usage stands firmly at 5GB, hasn't gone above that the whole day today.
Xeon(R) CPU E5-1650 v3
64GB DDR4 ECC RAM
2 x 240GB SSDs (Software Raid 1)
Code: Select all
[server] [mysqld] skip_name_resolve default_storage_engine = InnoDB tmp_table_size = 512M max_heap_table_size = 512M max_connect_errors = 10000 innodb_flush_method = O_DIRECT innodb_log_files_in_group = 2 innodb_log_file_size = 512M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 15G innodb_buffer_pool_instances = 15 innodb_log_buffer_size = 128M innodb_write_io_threads = 8 innodb_read_io_threads = 8 # LOGGING # log_error = /var/log/mysql/mysqld.log slow_query_log = 0 slow_query_log_file = /var/log/mysql/mysql-slow.log long_query_time = 1 #log_queries_not_using_indexes = 1 [galera] [embedded] [mariadb] [mariadb-10.1] [mysqld_safe]
What am I doing wrong? Please help!