Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>All of your MySQL variables seems very low. First of all the most important thing: what storage engine are you using? Key_buffer_size has only effect on <strong>MyISAM</strong> storage engine. </p> <p>If you're using <strong>MyISAM</strong> do the followings:</p> <pre><code>&gt; select sum(index_length) / 1024 / 1024 as index_size_MB from information_schema.Tables where Table_schema = 'knagy' and Engine = 'MyISAM'; +---------------+ | index_size_MB | +---------------+ | 0.16992188 | +---------------+ </code></pre> <p>This will show you how big your indexes are. You should set roughly this value as <strong>key_buffer_size</strong> if you have enough RAM. But don't increase this higher than 50-60% of your free RAM.</p> <p>If you're using <strong>InnoDB</strong> try to set the <strong>innodb_buffer_pool</strong> to the size of your dataset with indexes:</p> <pre><code>&gt; select sum(index_length + data_length) / 1024 / 1024 as innodb_MB from information_schema.Tables where Table_schema = 'knagy' and Engine = 'InnoDB'; +--------------+ | innodb_MB | +--------------+ | 403.04687500 | +--------------+ </code></pre> <p>You can set it up to 80% of your free RAM of course consider that other application's memory usage.</p> <p>Only with one of these changes you will get significant performance boost.</p> <p>You can increase the <strong>thread_cache_size</strong> as well around 30-50 or more if you see <strong>threads_created</strong> status variable increasing fast.</p> <p>Of course there are a lot of further optimizations but this will get you around the 80-90% of the possible maximum performance.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload