2. Cacti
3. core (v1.2.x)
4. English
5. Zen

3720 lib/utility.php:1047
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M. 159/10000 · 159 Needs editing
3721 lib/utility.php:1053
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10%% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status. 764/10000 · 764 Needs editing
3722 lib/utility.php:1059
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. 103/10000 · 103 Needs editing
3723 lib/utility.php:1065 • lib/utility.php:1071
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 538/10000 · 538 Needs editing
3724 lib/utility.php:1077
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 312/10000 · 312 Needs editing
3725 lib/utility.php:1083
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 169/10000 · 169 Needs editing
3726 lib/utility.php:1089
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 213/10000 · 213 Needs editing
3727 lib/utility.php:1095
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 405/10000 · 405 Needs editing
3728 lib/utility.php:1101
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 349/10000 · 349 Needs editing
3729 lib/utility.php:1106
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This is where metadata is stored. If you had a lot of tables, it would be useful to increase this. 98/10000 · 98 Needs editing
3730 lib/utility.php:1111
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system. 116/10000 · 116 Needs editing
3731 lib/utility.php:1116
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Maximum I/O performance happens when you use the O_DIRECT method to flush pages. 80/10000 · 80 Needs editing
3732 lib/utility.php:1126
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 149/10000 · 149 Needs editing
3733 lib/utility.php:1131
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — With modern SSD type storage, having multiple io threads is advantageous for applications with high io characteristics. 119/10000 · 119 Needs editing
3734 lib/utility.php:1139 • lib/utility.php:1181
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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 200/10000 · 200 Needs editing
3735 lib/utility.php:1144
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 285/10000 · 285 Needs editing
3736 lib/utility.php:1149
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 286/10000 · 286 Needs editing
3737 lib/utility.php:1155
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — %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. 378/10000 · 378 Needs editing
3738 lib/utility.php:1155
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — %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. 393/10000 · 393 Needs editing
3739 lib/utility.php:1161 • lib/utility.php:1197
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 211/10000 · 211 Needs editing