[rrd-users] Re: Maximum Argument Length?

[Cliff Daniel]

Alex van den Bogaerdt <alex at slot.hollandcasino.nl> writes:

> Perhaps I missed something but what is wrong with:

I probably did a poor job explaining what I'm actually 
doing currently:

[standard graph defs]
.
.
DEF:in1=1.ports.rrd:ds0:AVERAGE 
DEF:mx1=1.ports.rrd:ds0:MAX
DEF:in2=2.ports.rrd:ds0:AVERAGE 
DEF:mx2=2.ports.rrd:ds0:MAX
DEF:in3=3.ports.rrd:ds0:AVERAGE 
DEF:mx3=3.ports.rrd:ds0:MAX
DEF:in4=4.ports.rrd:ds0:AVERAGE 
DEF:mx4=4.ports.rrd:ds0:MAX
DEF:in5=5.ports.rrd:ds0:AVERAGE 
DEF:mx5=5.ports.rrd:ds0:MAX
.
.
.
DEF:in282=282.ports.rrd:ds0:AVERAGE 
DEF:mx282=282.ports.rrd:ds0:MAX
CDEF:tin=in1,in2,+,in3,+,in4,+,in5....in282,+
CDEF:tmx=mx1,mx2,+,mx3,+,mx4,+,mx5....mx282,+

That's how I'm currently doing it... It gets those values
from 282 data sources 2 times.  I'm not sure the internals
to the data base but it would be cool to be able to maybe
do a DEF:(min1,avg1,max1)=your.rrd:ds0:MIN,AVERAGE,MAX
That would save a redundant lookups.

Anyway, my original concern is should I continue to read those
DS dynamically to build a global graph or perhaps should I start
thinking of maintaing a rrd that sums all the parts and updates
into  the global rrd?

Regards,
-- 
Cliff Daniel
Level 3 Communications

--
* To unsubscribe from the rrd-users mailing list, send a message with the
  subject: unsubscribe to rrd-users-request at list.ee.ethz.ch