Hello,
> OK, I'm going to play devil's advocate here: WHY is it not a good idea?
>   Rateup would create the graphs all the time anyway.  By switching to
> rrdtool, I get more disk IO efficiency because of the database format.

1. This is not a good idea, because you need much processor time for graph
generating. For example, I have 6500 targets * four graphs = 26000 
pictures/5min.
2. 14all is a PERL script. I use modPerl in Apache. Without something like
modperl you've got bad performance.
3. This is double work probably.

> I was looking for an example of the exact call to "rrdtool graph", not
> ANOTHER pointer to use the CGI.

OK at attachment (If mailing list doesn't break it) I send you debug from 
14all.cgi script.

> get into production).  So, I'd like to migrate to RRDTool for logging
> with graphs created always, and then migrate to RRDTool with cgi-based
> graph creation.

I was write my own html index maker, which I run every 24 hours after
cfgmaker. Next I have small stupid PERL CGI script, which make possible
pattern search from HTML pages. For example descriptions from router
interfaces. 

> I too have one config per router.  But at nearly 200KB and over 4000
> lines, I will probably still have a slow-to-read configuration.

Some my configs have about 400kB and graphs are generated to 1 second.
My greates problem was harddisk performance, but now I'am happy with
SCSI Ultra320 controller with 64MB cache and harddisk with 15000RPM.

Best regards,

Pavel Ruzicka


-- Attached file removed by Ecartis and put at URL below --
-- Type: text/plain
-- Size: 4k (4432 bytes)
-- URL : http://www.ee.ethz.ch/~slist/p/14log.txt


--
Unsubscribe mailto:rrd-users-request@list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request@list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi