Contributing to this translation requires agreeing to its contributor agreement.
Zen

Translation

Especially on a system with a lot of writes to InnoDB tables you shouldIt is usually sufficient to set {innodb_log_file_size} to 25%% of the size of {innodb_buffer_pool_size}. However the bigger this value, the longerA very big {innodb_log_file_size} slows down the recovery time will be whenafter a database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable considerably. See also <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
It is usually sufficient to set {innodb_log_file_size} to 25% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows down the recovery time after a database crash considerably. See also <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
610/6170 · 617

Contributing to this translation requires agreeing to its contributor agreement.

English Slovak Actions
The InnoDB log file size is not an appropriate size, in relation to the InnoDB buffer pool.
Veľkosť logu InnoDB nemá správnu veľkosť v porovnaní s bufferom InnoDB.
Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
Špeciálne na systéme ktorý zapisuje veľa do tabuliek InnoDB mali by ste nastaviť {innodb_log_file_size} na 25%% z {innodb_buffer_pool_size}. Čím vyššie číslo, tím dlhšie sa bude obnovovať ak databáza crashne, takže toto číslo by nemalo byť vyššie než 256 MiB. Všimnite si že nemôžete jednoducho zmeniť hodnotu. Musíte vypnúť server, vymazať log súbory InnoDB, nastaviť novú hodnotu v my.cnf, zapnúť server, skontrolovať či nenastali v logu či je všetko v poriadku. Taktiež pozrite <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">tento príspevok</a>
Your InnoDB log size is at %s%% in relation to the InnoDB buffer pool size, it should not be below 20%%
Veľkosť logu InnoDB je %s%% v porovnaní s bufferom InnoDB, nemala by byť menšia ako 20%%
Max InnoDB log size
Maximálna veľkosť logu InnoDB
The InnoDB log file size is inadequately large.
Veľkosť záznamového súboru je príliš veľká.
It is usually sufficient to set {innodb_log_file_size} to 25% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows down the recovery time after a database crash considerably. See also <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
Špeciálne na systéme ktorý zapisuje veľa do tabuliek InnoDB mali by ste nastaviť {innodb_log_file_size} na 25%% z {innodb_buffer_pool_size}. Čím vyššie číslo, tím dlhšie sa bude obnovovať ak databáza crashne, takže toto číslo by nemalo byť vyššie než 256 MiB. Všimnite si že nemôžete jednoducho zmeniť hodnotu. Musíte vypnúť server, vymazať log súbory InnoDB, nastaviť novú hodnotu v my.cnf, zapnúť server, skontrolovať či nenastali v logu či je všetko v poriadku. Taktiež pozrite <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">tento príspevok</a>
Your absolute InnoDB log size is %s MiB
Veľkosť záznamov InnoDB je %s MiB
InnoDB buffer pool size
Veľkosť buffera InnoDB
Your InnoDB buffer pool is fairly small.
Váš buffer InnoDB je primalý.
The InnoDB buffer pool has a profound impact on performance for InnoDB tables. Assign all your remaining memory to this buffer. For database servers that use solely InnoDB as storage engine and have no other services (e.g. a web server) running, you may set this as high as 80% of your available memory. If that is not the case, you need to carefully assess the memory consumption of your other services and non-InnoDB-Tables and set this variable accordingly. If it is set too high, your system will start swapping, which decreases performance significantly. See also <a href="https://www.percona.com/blog/2007/11/03/choosing-innodb_buffer_pool_size/">this article</a>
 
You are currently using %s%% of your memory for the InnoDB buffer pool. This rule fires if you are assigning less than 60%%, however this might be perfectly adequate for your system if you don't have much InnoDB tables or other services running on the same machine.
 

Loading…

User avatar None

Source string changed

  1. phpMyAdmin
  2. 5.1
  3. Slovak
Especially on a system with a lot of writes to InnoDB tables you shouldIt is usually sufficient to set {innodb_log_file_size} to 25%% of the size of {innodb_buffer_pool_size}. However the bigger this value, the longerA very big {innodb_log_file_size} slows down the recovery time will be whenafter a database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable considerably. See also <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
3 years ago
Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English Slovak
log log phpMyAdmin

String information

Flags
no-php-format
Source string location
libraries/advisory_rules_generic.php:675
String age
3 years ago
Last updated
12 months ago
Source string age
3 years ago
Translation file
po/sk.po, string 160