Skip to main content

Mysql server memory variables

join_buffer_size: (PER SESSION) Controls the amount of memory allocated to perform joins on tables that have no keys which can be used to perform a condition filter. Allocated for each table joined without necessary filter conditions.

key_buffer_size: (GLOBAL) (MyISAM-only) Controls the amount of memory allocated to the MyISAM index key cache.

innodb_buffer_pool_size: (GLOBAL) (InnoDB-only) Controls the amount of memory allocated to the InnoDB cache containing both clustered data and secondary index pages.

innodb_additional_mem_pool_size: (GLOBAL) (InnoDB-only) Controls the amount of memory allocated to the buffer storing the InnoDB internal data dictionary.

innodb_log_buffer_size: (GLOBAL) (InnoDB-only) Controls the amount of memory allocated to the buffer storing InnoDB write-ahead log entries.

query_cache_size: (GLOBAL) Controls the amount of memory allocated to the Query Cache.

read_buffer_size: (PER SESSION) Controls the amount of memory allocated to the connecting thread in order to process a table scan.

read_rnd_buffer_size: (PER SESSION) Controls the amount of memory allocated to the buffer used to read previously sorted results.

sort_buffer_size: (PER SESSION) Controls the amount memory allocated to the buffer used to sort result sets before returning the set to the calling client.

thread_stack: (PER SESSION) Controls the default stack memory allocated for each connecting thread.

tmp_table_size: (GLOBAL) Controls the maximum memory to allocate to a temporary table before MySQL converts it into an on-disk MyISAM table.

thread_cache_size: (GLOBAL) Determines the number of thread connection objects that MySQL keeps in a cache to mitigate resource creation costs.

Comments

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three