[rrd-users] [unsure] max DS per rrd file

[David Thornton]

I try to group the collection in logical units: 15 sql vars per host -> 1
file. 25 smtp variables per host -> 1 file. 1500 hosts? 3000 files. Each
host writes two files. It spreads well.

Later I move those files centrally and start "looking" at
them. Separating collection from reporting is big. There is a trade off,
making the collection nice and light , my reporting is has more latency in
it, both in the time before I get data, and the complexity and time to
compose the report. google "olap versus oltp".

David Thornton


On Sat, Apr 20, 2013 at 7:48 AM, mikel <infoeuskadi at gmail.com> wrote:

>
> Thanks for your fast reply again.
>
> >Maybe I don't understand what you say here. Some metrics, or all metrics
> are
> >queried? Both statements cannot be true at the same time?
>
> Yes it is a tricky case. Apologies I was not clear enough.
>
> In most cases all metrics are queried at the same time, because we want to
> know what value they had at a given time. And classify them.
>
> Very randomly we would query for just one metric.
>
> >Anyway, if you query only once in a while, maybe you should think about
> >reducing the number of RRAs in each RRD, and just let it consolidate at
> >graph time. Yes, this will mean you will have to wait longer for your
> graph
> >to be made, but you save processing time at every update.
>
> This is interesting I did not think about that. Thanks for the hint.
>
> Thanks for your help again.
> m
>
>
>
> --
> View this message in context:
> http://rrd-mailinglists.937164.n2.nabble.com/max-DS-per-rrd-file-tp7580966p7580971.html
> Sent from the RRDtool Users Mailinglist mailing list archive at Nabble.com.
>
> _______________________________________________
> rrd-users mailing list
> rrd-users at lists.oetiker.ch
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/rrd-users/attachments/20130420/e32ca495/attachment.htm