|
rename %s to %s
|
|
ERROR while writing XML file: %s
|
|
ERROR: RRDfile %s not writeable
|
|
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file
|
|
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file
|
|
Website does not have write access to %s, may be unable to create/update RRDs
|
|
Failed to open data file, poller may not have run yet
|
|
Graph Not created for %s due to bad data
|
|
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
|
|
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
|
|
It is recommended that you enable InnoDB in any %s version greater than 5.1.
|
|
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.
|
|
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.
|
|
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
|
|
%s Tuning
|
|
Note: Many changes below require a database restart
|
|
PHP %s is the minimum version
|
|
A minimum of %s memory limit
|
|
A minimum of %s m execution time
|
