2. Cacti
3. core
4. English
5. Zen

4305 lib/utility.php:1196
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts. 327/10000 · 327 Needs editing
4306 lib/utility.php:1201
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Keeping the table cache larger means less file open/close operations when using innodb_file_per_table. 102/10000 · 102 Needs editing
4307 lib/utility.php:1206
	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
4308 lib/utility.php:1212
	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
4309 lib/utility.php:1218
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. 103/10000 · 103 Needs editing
4310 lib/utility.php:1224
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If this number is negative, reduce the innodb_buffer_pool_size until the join_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the systems memory if the database is separate from the Cacti web server. However, try to not go below the default of 262,144. 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 database is hosted on the Cacti web server and less if you intend to have very large RRDfiles or hundreds of thousands to millions long term. 926/10000 · 926 Needs editing
4311 lib/utility.php:1230
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — If this number is negative, reduce the innodb_buffer_pool_size until the sort_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the system memory if the database is separate from the Cacti web server. However, try to not go below the default setting of 2,097,152. A sort buffer performs sorts for some queries using ORDER BY or GROUP BY. Configuring sort_buffer_size decides how much memory will be allocated for sort queries. The sort_buffer_size may need to be adjusted from the default if the workload requires a significant number of sort queries. The sort_buffer_size is defined on a per-session variable. Use the same equation as that of the join_buffer_size to determine the per connection possible memory. 846/10000 · 846 Needs editing
4312 lib/utility.php:1236
	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
4313 lib/utility.php:1242
	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
4314 lib/utility.php:1248
	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
4315 lib/utility.php:1254
	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. If you database is very large or remote, you can consider increasing this size. If remote, it can by as high as 80% of the systems memory. However, cautions must be taken to reduce the swappiness of the system, or to remove swap to keep the system from swapping. 671/10000 · 671 Needs editing
4316 lib/utility.php:1260
	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 accommodate 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. 350/10000 · 350 Needs editing
4317 lib/utility.php:1265
	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
4318 lib/utility.php:1270
	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
4319 lib/utility.php:1275
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Maximum I/O performance happens when you use the O_DIRECT method to flush pages. 80/10000 · 80 Needs editing
4320 lib/utility.php:1285
	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
4321 lib/utility.php:1290
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — With modern SSD type storage, having multiple io threads is advantageous for applications with high io characteristics. 119/10000 · 119 Needs editing
4322 lib/utility.php:1298 • lib/utility.php:1340
	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
4323 lib/utility.php:1303
	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
4324 lib/utility.php:1308
	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