Jump to content

MySQL Optimization, advice?


Recommended Posts

Hi,

I recently started getting a noticeable slow down while using any related query action while navigating trough forums. Database itself is ~700 MB where largerst table are topics/posts ~283 MB.

I run 4.7.4 version This is my.ini config. Any advice of how to improve it?

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port		= xxxx
socket		= /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket		= /var/run/mysqld/mysqld.sock
nice		= 0

[mysqld]
#
# * Basic Settings
#
user		= mysql
pid-file	= /var/run/mysqld/mysqld.pid
socket		= /var/run/mysqld/mysqld.sock
port		= xxxx
basedir		= /usr
datadir		= /var/lib/mysql
tmpdir		= /tmp
lc-messages-dir	= /usr/share/mysql
skip-external-locking

#collation-server = utf8_general_ci
#character-set-server = utf8

skip-host-cache
#skip-name-resolve
# end added

#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address		= 0.0.0.0
#
# * Fine Tuning
#
max_allowed_packet	= 16M
thread_stack		= 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
#query_cache_limit	= 1M
#query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
general_log_file        = /var/log/mysql/mysql.log
general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries	= /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id		= 1
#log_bin			= /var/log/mysql/mysql-bin.log
expire_logs_days	= 10
max_binlog_size         = 100M
#binlog_do_db		= include_database_name
#binlog_ignore_db	= include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

default-storage-engine                = innodb
innodb_thread_concurrency             = 4

innodb_log_file_size                  = 100M
innodb_log_buffer_size                = 6M
sync_binlog                           = 1

innodb_buffer_pool_size               = 512M

innodb_flush_method                   = O_DIRECT #O_DSYNC
innodb_flush_log_at_trx_commit        = 2
innodb_lock_wait_timeout              = 120

innodb_file_per_table                 = 1

#Tried the following parameters to no good effect, actually (very) small decrease in performance,
#thus they are commented out but document here, just because.
#innodb_data_home_dir = /path/to/mysql
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /path/to/mysql
#transaction-isolation=READ-COMMITTED

#server-id=1
#log_bin=authdbmain-bin
#log_error=mysql-authdbmain.err
#binlog_do_db=authdbmain
#end of config added

show_compatibility_56 = 1

[mysqldump]
quick
quote-names
max_allowed_packet	= 16M

[mysql]
#no-auto-rehash	# faster start of mysql but no tab completition

[isamchk]
key_buffer		= 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

I have 10 GB RAM availble.

I noticed general problem of MySQL while interacting with forums DB. Issue started out of nowhere during last weekend where on Friday was all fine. Whenever I to to load the forums DB in PHPMyAdmin it takes more time than usually.

No SQL Error logs, no other symptoms or starting points. No machine issues, all other services and DB related things are smooth (based on same SQL server but different database).

I also have topics and posts tables on MyISAM engine (left post IPB3.4 upgrade). It was set to MyISAM to resolve large tables performance issue on IPB3.4. Should I covert them to InnoDB?

Link to comment
Share on other sites

1. You should try this: https://github.com/major/MySQLTuner-perl  - Once you have DB uptime for 2-3 days. Change/tune and monitor. May be share the output of above. Do note: For joins it will ask you to increase join_buffer_size but you can skip that suggestion. Sharing my sample output:

-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 0
[OK] InnoDB File per table is activated
[OK] InnoDB buffer pool / data size: 8.0G/5.3G
[OK] Ratio InnoDB log file size / InnoDB Buffer pool size: 1.0G * 2/8.0G should be equal to 25%
[OK] InnoDB buffer pool instances: 8
[--] Number of InnoDB Buffer Pool Chunk : 64 for 8 Buffer Pool Instance(s)
[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
[OK] InnoDB Read buffer efficiency: 100.00% (13346625516 hits/ 13346863880 total)
[OK] InnoDB Write log efficiency: 91.10% (11968155 hits/ 13136819 total)
[OK] InnoDB log waits: 0.00% (0 waits / 1168664 writes)

2. InnoDB - Yes. 

3. Install netdata. It's free and will help you with further details. 

https://www.netdata.cloud/

Example .. to monitor locks, Innodb stats, etc. 

Could contain: Chart

4. Enable slow query logs - This way you can monitor which queries are taking longer.

 

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...