No strings found!
Exit Zen
3714
lib/utility.php:966
English
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
47/870 · 87
3715
lib/utility.php:979 • lib/utility.php:1016
English
When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte.
120/1610 · 161
3716
lib/utility.php:985 • lib/utility.php:991 • lib/utility.php:1022 • lib/utility.php:1028
English
When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
119/1490 · 149
3717
lib/utility.php:1004
English
It is recommended that you enable InnoDB in any %s version greater than 5.1.
47/760 · 76
3718
lib/utility.php:1037
English
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.
264/3270 · 327
3719
lib/utility.php:1042
English
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table.
102/1020 · 102
3720
lib/utility.php:1047
English
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.
127/1590 · 159
3721
lib/utility.php:1053
English
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.
630/7640 · 764
3722
lib/utility.php:1059
English
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
91/1030 · 103
3723
lib/utility.php:1065 • lib/utility.php:1071
English
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.
0/5380 · 538
3724
lib/utility.php:1077
English
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.
246/3120 · 312
3725
lib/utility.php:1083
English
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.
149/1690 · 169
3726
lib/utility.php:1089
English
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.
191/2130 · 213
3727
lib/utility.php:1095
English
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.
320/4050 · 405
3728
lib/utility.php:1101
English
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.
306/3490 · 349
3729
lib/utility.php:1106
English
This is where metadata is stored. If you had a lot of tables, it would be useful to increase this.
81/980 · 98
3730
lib/utility.php:1111
English
Rogue queries should not for the database to go offline to others. Kill these queries before they kill your system.
104/1160 · 116
3731
lib/utility.php:1116
English
Maximum I/O performance happens when you use the O_DIRECT method to flush pages.
73/800 · 80
3732
lib/utility.php:1126
English
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.
115/1490 · 149
3733
lib/utility.php:1131
English
With modern SSD type storage, having multiple io threads is advantageous for applications with high io characteristics.
96/1190 · 119