Verdant TCS
Get support
Contact Us
Verdant TCS
Get support
Contact Us

Configure MySQL

  • UPDATED August 24, 2022
8 min read

Index

Configuration file and using these commands
MySQL Variables

Configuration File and using these commands

These changes are recorded in the mysqld.cnf which resides at the following filepath:

/etc/mysql/mysql.conf.d/mysqld.cnf

Settings configured in a mysqld.cnf are global by nature and impact each WordPress site using the MySQL server. If you have sites which have drastically different demands of the Database then it might be best to separate such sites into servers that contain sites sharing similar profiles. This way you can more effectively tune MySQL as per the demands of your WordPress sites.

GP-CLI Stack MySQL commands do not reload configuratoins immediately, this is because MySQL needs to stop and restart to load in new configurations. Therefore if you are going to make several changes it might be best to chain commands together and use a reload/restart command.

For example:

gp stack mysql -max-connections 100 &&  
gp stack mysql -innodb-buffer-pool-size 2048 && 
gp stack mysql -innodb-buffer-pool-instances 2 && 
gp mysql restart

MySQL Server Variables 

SET THE BINARY LOG (BINLOG) EXPIRATION PERIOD.

Sets the binary log expiration period in seconds. After their expiration period ends, binary log files can be automatically removed. Possible removals happen at startup and when the binary log is flushed.

Variable: binlog_expire_logs_seconds
Unit: Seconds
Default value: 2592000
Accepted values: 0-4294967295

gp stack mysql -binlog-expire-logs-seconds {accepted.value}

Example:

gp stack mysql -binlog-expire-logs-seconds 86400

back to top ▲

SET THE LOCK MODE TO USE FOR GENERATING AUTO-INCREMENT VALUES

The lock mode to use for generating auto-increment values. Permissible values are 0, 1, or 2, for traditional, consecutive, or interleaved, respectively.

Variable: innodb_autoinc_lock_mode
Default value: 1
Accepted values: 0 (traditional), 1 (consecutive), 2 (interleaved)

gp stack mysql -innodb-autoinc-lock-mode {accepted.value}

Example:

gp stack mysql -innodb-autoinc-lock-mode 2

back to top ▲

SET THE NUMBER OF INNODB BUFFER POOL INSTANCES

The number of regions that the InnoDB buffer pool is divided into. For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages.

This option only takes effect when setting innodb_buffer_pool_size to 1GB or more. The total buffer pool size is divided among all the buffer pools. For best efficiency, specify a combination of innodb_buffer_pool_instances and innodb_buffer_pool_size so that each buffer pool instance is at least 1GB.

Variable: innodb_buffer_pool_instances
Unit: GB
Default value: 8 (or 1 if innodb_buffer_pool_size < 1GB)
Accepted values: 1 – 64

gp stack mysql -innodb-buffer-pool-instances {accepted.value}

Example:

gp stack mysql -innodb-buffer-pool-instances 2

back to top ▲

SET THE SIZE OF THE INNODB BUFFER POOL INSTANCES

The size in bytes of the buffer pool, the memory area where InnoDB caches table and index data. The maximum value is 18446744073709551615 (264-1) bytes on 64-bit systems. When the size of the buffer pool is greater than 1GB, setting innodb_buffer_pool_instances to a value greater than 1 can improve the scalability on a busy server.

Variable: innodb_buffer_pool_size
Unit: MB
Default value:  64 MB if the total RAM is less than 1200MB at the time the server is provisioned, or 128MB if more.
Accepted values: 5 – 18446744073709

gp stack mysql -innodb-buffer-pool-size {accepted.value}

Example:

gp stack mysql -innodb-buffer-pool-size 2048

back to top ▲

CONTROLS THE BALANCE BETWEEN STRICT ACID COMPLIANCE AND HIGHER PERFORMANCE

Controls the balance between strict ACID compliance for commit operations and higher performance that is possible when commit-related I/O operations are rearranged and done in batches.

  • The default setting of 1 is required for full ACID compliance. Logs are written and flushed to disk at each transaction commit.
  • With a setting of 0, logs are written and flushed to disk once per second. Transactions for which logs have not been flushed can be lost in a crash.
  • With a setting of 2, logs are written after each transaction commit and flushed to disk once per second. Transactions for which logs have not been flushed can be lost in a crash.

Variable: innodb_flush_log_at_trx_commit
Default value: 1
Accepted values: 0, 1, 2

gp stack mysql -innodb-flush-log-at-trx-commit {accepted.value}

Example:

gp stack mysql -innodb-flush-log-at-trx-commit 2

back to top ▲

DEFINE THE METHOD USED TO FLUSH DATA TO INNODB DATA FILES AND LOG FILES

Defines the method used to flush data to InnoDB data files and log files, which can affect I/O throughput.

  • fsync – InnoDB uses the fsync() system call to flush both the data and log files.
  • O_DSYNC – InnoDB uses O_SYNC to open and flush the log files, and fsync() to flush the data files. InnoDB does not use O_DSYNC directly because there have been problems with it on many varieties of Unix.
  • littlesync – This option is used for internal performance testing and is currently unsupported. Use at your own risk.
  • nosync – This option is used for internal performance testing and is currently unsupported. Use at your own risk.
  • O_DIRECT – InnoDB uses O_DIRECT to open the data files, and uses fsync() to flush both the data and log files.
  • O_DIRECT_NO_FSYNC – InnoDB uses O_DIRECT during flushing I/O, but skips fsync() system call after each write operation.

Variable: innodb_flush_method
Default value: O_DIRECT
Accepted values: fsync, O_DSYNC, littlesync, nosync, O_DIRECT, O_DIRECT_NO_FSYNC

gp stack mysql -innodb-flush-method {accepted.value}

Example:

gp stack mysql -innodb-flush-method O_DSYNC

back to top ▲

DEFINE THE STANDARD NUMBER OF IOPS AVAILABLE TO INNODB BACKGROUND TASKS

The innodb_io_capacity variable defines the number of I/O operations per second (IOPS) available to InnoDB background tasks, such as flushing pages from the buffer pool and merging data from the change buffer.

Variable: innodb_io_capacity
Default value: 1000
Accepted values: 1 – 1.8446744e+19 

gp stack mysql -innodb-io-capacity {accepted.value}

Example:

gp stack mysql -innodb-io-capacity 500

back to top ▲

DEFINE THE MAXIMUM NUMBER OF IOPS AVAILABLE TO INNODB BACKGROUND TASKS

If flushing activity falls behind, InnoDB can flush more aggressively, at a higher rate of I/O operations per second (IOPS) than defined by the innodb_io_capacity variable. The innodb_io_capacity_max variable defines a maximum number of IOPS performed by InnoDB background tasks in such situations.

Variable: innodb_io_capacity_max
Default value: 2000
Accepted values: 1 – 1.8446744e+19 

gp stack mysql -innodb-io-capacity-max {accepted.value}

Example:

gp stack mysql -innodb-io-capacity-max 2500

 

back to top ▲

DEFINE THE SIZE OF EACH LOG FILE IN A LOG GROUP

The size in bytes of each log file in a log group. The combined size of log files (innodb_log_file_size * innodb_log_files_in_group) cannot exceed a maximum value that is slightly less than 512GB. A pair of 255 GB log files, for example, approaches the limit but does not exceed it.

Variable: innodb_log_file_size
Unit: MB
Default value: 100
Accepted values: 512GB / innodb_log_files_in_group

gp stack mysql -innodb-log-file-size {accepted.value}

Example:

gp stack mysql -innodb-log-file-size 256

back to top ▲

DEFINE THE MINIMUM BUFFER SIZE USED TO SCAN INDEXES AND JOINS THAT DO NOT USE INDEXES

The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use indexes and thus perform full table scans. Normally, the best way to get fast joins is to add indexes. Increase the value of join_buffer_size to get a faster full join when adding indexes is not possible. One join buffer is allocated for each full join between two tables. For a complex join between several tables for which indexes are not used, multiple join buffers might be necessary.

Variable: join_buffer_size
Unit: KB
Default value: 256
Accepted values: 128 – 18446744073709547520

gp stack mysql -join-buffer-size {accepted.value}

Example:

gp stack mysql -join-buffer-size 512

 

back to top ▲

DEFINE THE MINIMUM TIME TO BE RECOGNISED AS A LONG QUERY FOR SLOW QUERY LOGGING

If a query takes longer than this many seconds, the server increments the slow_queries status variable. If the slow query log is enabled, the query is logged to the slow query log file. This value is measured in real time, not CPU time, so a query that is under the threshold on a lightly loaded system might be above the threshold on a heavily loaded one. The minimum and default values of long_query_time are 0 and 10, respectively.

This setting requires slow_query_log to be enabled to do anything.

Variable: long_query_time
Unit: Seconds
Default value: 0 (but disabled)
Accepted values: 0+

gp stack mysql -long-query-time {accepted.value}

Example:

gp stack mysql -long-query-time 512

 

back to top ▲

DEFINE THE MAXIMUM SIZE OF A BINLOG FILE UNDER NORMAL CIRCUMSTANCES*

If a write to the binary log causes the current log file size to exceed the value of this variable, the server rotates the binary logs (closes the current file and opens the next one). The minimum value is 4096 bytes. The maximum value is 1GB. Encrypted binary log files have an additional 512-byte header, which is included in max_binlog_size.

*A transaction is written in one chunk to the binary log, so it is never split between several binary logs. Therefore, if you have big transactions, you might see binary log files larger than max_binlog_size.

Variable: max_binlog_size
Unit: MB
Default value: 100
Accepted values: 1 – 1000

gp stack mysql -max-binlog-size {accepted.value}

Example:

gp stack mysql -max-binlog-size 512

back to top ▲

DEFINE THE MAXIMUM NUMBER OF SIMULTANEOUS CLIENT CONNECTIONS TO THE MYSQL SERVER

The maximum permitted number of simultaneous client connections to the MySQL server.

Variable: max_connections
Unit: Integer
Default value: 200
Accepted values: 1 – 100000

gp stack mysql -max-connections {accepted.value}

Example:

gp stack mysql -max-connections 151

back to top ▲

ENABLE/DISABLE THE SLOW QUERY LOG.

Whether the slow query log is enabled. The value can be 0 (or OFF) to disable the log or 1 (or ON) to enable the log. This function will also enable the long_query_time of 0 seconds, you may wish to also adjust this variable.

Variable: slow_query_log
Unit: Boolean
Default value: 0 (OFF)
Accepted values: 0 (OFF), 1 (ON)

gp stack mysql -slow-query-log {accepted.value}

Example:

gp stack mysql -slow-query-log 1

MySQL slow query log output can be viewed in the following log:

/var/log/mysql/slow.log

 

back to top ▲

DETERMINE HOW THE SERVER HANDLES THREADS FOR CLIENT CONNECTIONS 

Determines how the server handles threads for client connections. In addition to threads for client connections, this also applies to certain internal server threads, such as Galera slave threads.

  • When the default one-thread-per-connection mode is enabled, the server uses one thread to handle each client connection.
  • When the pool-of-threads mode is enabled, the server uses the thread pool for client connections.
  • When the no-threads mode is enabled, the server uses a single thread for all client connections, which is really only usable for debugging.

Variable: thread_handling
Default value: one-thread-per-connection
Accepted values: one-thread-per-connection, no-threads, pool-of-threads

gp stack mysql -thread-handling {accepted.value}

Example:

gp stack mysql -thread-handling pool-of-threads

back to top ▲

 

MANAGE THE THREAD POOL HIGH PRIORITY SCHEDULING MODE

This variable is used to provide more fine-grained control over high priority scheduling either globally or per connection.

  • Transactions. In this mode, only statements from already started transactions may go into the high priority queue depending on the number of high priority tickets currently available in a connection.
  • Statements. In this mode, all individual statements go into the high priority queue, regardless of connection’s transactional state and the number of available high priority tickets. This value can be used to prioritize AUTOCOMMIT transactions or other kinds of statements such as administrative ones for specific connections. Note that setting this value globally essentially disables high priority scheduling, since in this case all statements from all connections will use a single queue (the high priority one)
  • None. This mode disables high priority queue for a connection. Some connections (e.g. monitoring) may be insensitive to execution latency and/or never allocate any server resources that would otherwise impact performance in other connections and thus, do not really require high priority scheduling. Note that setting thread_pool_high_prio_mode to none globally has essentially the same effect as setting it to statements globally: all connections will always use a single queue (the low priority one in this case).

Variable: thread_pool_high_prio_mode
Default value: transactions
Accepted values: transactions, statements, none

gp stack mysql -thread-pool-high-prio-mode {accepted.value}

Example:

gp stack mysql -thread-pool-high-prio-mode statements

This variable is inactive unless thread_handling is set to pool-of-threads 

back to top ▲

ASSIGN THE NUMBER OF TICKETS IN THE HIGH PRIORITY QUEUE POLICY 

This variable controls the high priority queue policy. Each new connection is assigned this many tickets to enter the high priority queue. Setting this variable to 0 disables the high priority queue.

Variable: thread_pool_high_prio_tickets
Unit: Integer
Default value: 4294967295

gp stack mysql -thread-pool-high-prio-tickets {accepted.value}

Example:

gp stack mysql -thread-pool-high-prio-tickets statements

This variable is inactive unless thread_handling is set to pool-of-threads

back to top ▲

LIMIT THE TIME AN IDLE THREAD SHOULD WAIT BEFORE EXITING

This variable can be used to limit the time an idle thread should wait before exiting.

Variable: thread_pool_idle_timeout
Unit: Seconds
Default value: 60

gp stack mysql -thread-pool-idle-timeout {accepted.value}

Example:

gp stack mysql -thread-pool-idle-timeout 30

This variable is inactive unless thread_handling is set to pool-of-threads 

back to top ▲

LIMIT THE MAXIMUM NUMBER OF THREADS IN A POOL

This variable can be used to limit the maximum number of threads in the pool. Once this number is reached no new threads will be created.

Variable: thread_pool_max_threads
Unit: Integer
Default value: 100000

gp stack mysql -thread-pool-max-threads {accepted.value}

Example:

gp stack mysql -thread-pool-max-threads 150000

This variable is inactive unless thread_handling is set to pool-of-threads 

back to top ▲

DEFINE THE NUMBER OF THREADS THAT CAN USE THE CPU AT THE SAME TIME

This variable can be used to define the number of threads that can use the CPU at the same time.

Variable: thread_pool_size
Unit: Integer
Default value: Number of CPU Cores

gp stack mysql -thread-pool-size {accepted.value}

Example:

gp stack mysql -thread-pool-size 4

This variable is inactive unless thread_handling is set to pool-of-threads 

back to top ▲

DEFINE THE NUMBER OF MILLISECONDS BEFORE A RUNNING THREAD IS CONSIDERED STALLED

The number of milliseconds before a running thread is considered stalled. When this limit is reached thread pool will wake up or create another thread. This is being used to prevent a long-running query from monopolizing the pool.

Variable: thread_pool_stall_limit
Unit: Milliseconds
Default value: 500

gp stack mysql -thread-pool-stall-limit {accepted.value}

Example:

gp stack mysql -thread-pool-stall-limit 1000

This variable is inactive unless thread_handling is set to pool-of-threads

back to top ▲

Search the Knowledge Base

New to vCanopy?

Get started with our FREE Core plan today! We bring the software, you bring the hardware.
Create My Free Account