Tobias Oetiker wrote:

>  > The only way to do this is to store data covering the whole period
>>  you may want to chart over, and at the best resolution that you will
>>  ever want - you can't extract information later that you don't have
>>  stored. That's likely to be a huge store, and also not what rrd is
>>  about.
>
>Note that if you configure rrd to keep lots of hires values AS WELL
>AS lower res values for the SAME TIME PERIODE, then there will be
>no performance impact, only a huge disk space requirement.

Talking of which, is the storage requirement for an rrd database 
documented anywhere ?

Simon

--
Unsubscribe mailto:[EMAIL PROTECTED]
Help        mailto:[EMAIL PROTECTED]
Archive     http://lists.ee.ethz.ch/rrd-users
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi

Reply via email to