|
The amount of time Cacti will maintain the partitioned Flow tables.
|
仙人掌將維護分區流表的時間。
|
|
%d Week
|
％d週
|
|
%d Weeks
|
最後％d週
|
|
%d Month
|
%d月
|
|
%d Months
|
最後％d個月
|
|
%d Year
|
%d年
|
|
Database Partitioning Scheme
|
數據庫分區方案
|
|
Depending on the number of flows per minute, you may require more tables per day.
|
根據每分鐘的流數，您可能每天需要更多表。
|
|
Daily
|
每日
|
|
Hourly
|
每小時
|
|
Storage Engine for Raw Tables
|
原始表的儲存引擎
|
|
The Aria Engine is perfect for all but the Live raw table. The Live raw table will always be InnoDB. Take your pick.
|
Aria Engine 非常適合除 Live raw 表以外的所有內容。 Live raw 表將始終為 InnoDB。 任您挑選。
|
|
Aria (Fast, Crash Safe)
|
Aria（快速、碰撞安全）
|
|
InnoDB (Slow, High Concurrency)
|
InnoDB（慢速、高併發）
|
|
Parallel Queries
|
並行查詢
|
|
Max Concurrent Threads
|
最大併發線程數
|
|
The maximum number of threads that will be dispatched to run the FlowView queries. Note that you can have at most 1 thread per database partition, and you should be careful not to overload your database server with having too many concurrent threads running.
|
為運行 FlowView 查詢而調度的最大線程數。 請注意，每個資料庫分區最多可以有1個線程，並且應注意不要因運行過多的併發線程而使資料庫伺服器過載。
|
|
Disabled
|
停用
|
|
%d Threads
|
％d個主題
|
|
Maximum Run Time
|
最大行數
|
