If you don't make use of MyISAM tables at all, you can set this to a very low value, such as 64K. When using Kerberos, the header of the negotiate messages is large. The effective maximum size might be lower than what is set, depending on the server's available physical RAM and the per-process limit determined by the operating system. The best idea is to set the value of the InnoDB buffer pool size to 80 of the RAM. Choosing the proper size of the InnoDB buffer pool requires some knowledge of system memory. For slave clients, the size limit is 256M, persistent restriction when a client buffer size of 60 seconds more than 64M, the client connection is closed. Buffer pool helps MySQL/MariaDB queries be executed comparatively faster. The ratio of key_reads to key_read_requests should be as low as possible, 1:100 is the highest acceptable, 1:1000 is better, and 1:10 is terrible. MySQL/MariaDB has an InnoDB engine that has a buffer pool to cache and index data in the memory. Note that Aria tables by default make use of an alternative setting, aria-pagecache-buffer-size.ДЄ good rule of thumb for servers consisting particularly of MyISAM tables is for about 25% or more of the available server memory to be dedicated to the key buffer.ДЄ good way to determine whether to adjust the value is to compare the key_read_requests value, which is the total value of requests to read an index, and the key_reads values, the total number of requests that had to be read from disk. Key_buffer_size is a MyISAM variable which determines the size of the index buffers held in memory, which affects the speed of index reads.

Optimize connection buffer size