Zen

Translation

%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.
0/3930 · 393

Sign in to save translations.

English Ukrainian Actions
When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80%. If the recommendation is negative, you must decrease this and or the sort_buffer_size until the recommendation fits within the allowable memory.
 
When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.
 
When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables.
 
If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables.
 
InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25%% of your systems total memory, but your requirements will vary depending on your systems size.
 
This settings should remain ON unless your Cacti instances is running on either ZFS or FusionI/O which both have internal journaling to accomodate abrupt system crashes. However, if you have very good power, and your systems rarely go down and you have backups, turning this setting to OFF can net you almost a 50% increase in database performance.
 
This is where metadata is stored. If you had a lot of tables, it would be useful to increase this.
 
Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system.
 
Maximum I/O performance happens when you use the O_DIRECT method to flush pages.
 
Setting this value to 2 means that you will flush all transactions every second rather than at commit. This allows %s to perform writing less often.
 
With modern SSD type storage, having multiple io threads is advantageous for applications with high io characteristics.
 
As of %s %s, the you can control how often %s flushes transactions to disk. The default is 1 second, but in high I/O systems setting to a value greater than 1 can allow disk I/O to be more sequential
 
With modern SSD type storage, having multiple read io threads is advantageous for applications with high io characteristics. Depending on your MariaDB/MySQL versions, this value can go as high as 64. But try to keep the number less than your total SMT threads on the database server.
 
With modern SSD type storage, having multiple write io threads is advantageous for applications with high io characteristics. Depending on your MariaDB/MySQL versions, this value can go as high as 64. But try to keep the number less than your total SMT threads on the database server.
 
%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MariaDB less than 10.5. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max the number of CPU cores or 64.
 
%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.
 
If you have SSD disks, use this suggestion. If you have physical hard drives, use 200 * the number of active drives in the array. If using NVMe or PCIe Flash, much larger numbers as high as 100000 can be used.
 
If you have SSD disks, use this suggestion. If you have physical hard drives, use 2000 * the number of active drives in the array. If using NVMe or PCIe Flash, much larger numbers as high as 200000 can be used.
 
If you have SSD disks, use this suggestion. Otherwise, do not set this setting.
 
With modern SSD type storage, having multiple read io threads is advantageous for applications with high io characteristics.
 
With modern SSD type storage, having multiple write io threads is advantageous for applications with high io characteristics.
 
When using MariaDB 10.2.4 and above, this setting should be off if atomic writes are enabled. Therefore, please enable atomic writes instead of the double write buffer as it will increase performance.
 
When using MariaDB 10.2.4 and above, you can use atomic writes over the doublewrite buffer to increase performance.
 
%s Tuning
 
Note: Many changes below require a database restart
 
Variable
 
Current Value
 
Recommended Value
 
Comments
 
PHP %s is the minimum version
 
A minimum of %s memory limit
 
User avatar anonymous

Suggestion added

%s розділить innodb_buffer_pool на області пам’яті, щоб покращити продуктивність для версій MySQL до та включно з MySQL 8.0. Максимальне значення становить 64, але воно не повинно перевищувати кількість ядер/потоків ЦП. Якщо ваш innodb_buffer_pool менше 1 ГБ, ви повинні використовувати розмір пулу, поділений на 128 МБ. Продовжуйте використовувати це рівняння до максимальної кількості ядер ЦП або 64.

Suggested change:

%s розділить innodb_buffer_pool на області пам’яті, щоб покращити продуктивність для версій MySQL до та включно з MySQL 8.0. Максимальне значення становить 64, але воно не повинно перевищувати кількість ядер/потоків ЦП. Якщо ваш innodb_buffer_pool менше 1 ГБ, ви повинні використовувати розмір пулу, поділений на 128 МБ. Продовжуйте використовувати це рівняння до максимальної кількості ядер ЦП або 64.
2 months ago

Loading…

User avatar anonymous

Suggestion added
%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.
%s розділить innodb_buffer_pool на області пам’яті, щоб покращити продуктивність для версій MySQL до та включно з MySQL 8.0. Максимальне значення становить 64, але воно не повинно перевищувати кількість ядер/потоків ЦП. Якщо ваш innodb_buffer_pool менше 1 ГБ, ви повинні використовувати розмір пулу, поділений на 128 МБ. Продовжуйте використовувати це рівняння до максимальної кількості ядер ЦП або 64.
2 months ago
Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Glossary

English Ukrainian
No related strings found in the glossary.

533623 String information

Flags
php-format
Source string location
lib/utility.php:1155
String age
2 years ago
Last updated
3 months ago
Source string age
2 years ago
Translation file
locales/po/uk-UA.po, string 3738