Hi Yossi, On Thu, Jan 26, 2012 at 05:17:20AM -0800, Yossi Ozani wrote:
> - sql_history - "store" information as long as N time units . N is the > time slot(1m or 1h or ....) sql_history chops traffic aggregates into time-bins. If primitives that are selected via the 'aggregate' directive define a spatial aggregation, then sql_history defines a further dimension - temporal aggregation. > - sql_refresh_time - define a timer which trigger a procedure which, in > generally, copy the data stored in sql_history to my plugin(e.g. MySQL) Data gathered from the network is aggregated and cached in memory. The value of sql_refresh_time defines the time data is cached in memory before being written to the backend (ie. a MySQL database). While the two directives are independent, and unless some corner scenario is to be covered, recommendation is to let them coincide to optimize performances, ie. avoid issuing UPDATE SQL queries. Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
