|
%0.1f Minutes
|
%0.1f minutos
|
|
%d Changes
|
0 alterações
|
|
%d OID
|
OID
|
|
%d Processes
|
Processos
|
|
%d Repetitions
|
Repetições
|
|
%d seconds left.
|
{} segundos restantes
|
|
%s - N/A
|
N/A
|
|
%s - No
|
Alternado de %s para %s
|
|
%s Thread
|
Rosca
|
|
%s Threads
|
Threads
|
|
Current Page: %s
|
Página
|
|
Details %s
|
%s Detalhes
|
|
Graph: %s
|
Gráfico:
|
|
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.
|
|
|
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.
|
|
|
Main / Remote Status
|
ESTADO REMOTO
|
|
Met: %d
|
Met
|
|
No - %s
|
Alternado de %s para %s
|
|
Open a ticket at
|
Abra um ticket em:
|
|
Process: %d
|
Processo 0
|
