Perl RRDs 1.3 graphing deadly slow on Debian Etch.

[Raimund Berger]

Hi guys

as noted earlier, I recently installed rrdtool 1.3 on a Debian Etch
server, and after upgrading libcairo everything went fine from build
to rrdtool execution and performance on the command line.

I now tried some graphing with a couple of perl scripts using RRDs, in
and out of Apache, and things were deadly slow compared to command
line performance. Some perl profiling showed that the extra time is
actually spent in RRDs.

Glancing over the list, I've seen that at least one major patch has
been applied which might be hard to swallow for Etch's default Perl
install, the version being:

$ dpkg -l perl
ii  perl  5.8.8-7etch3   Larry Wall's Practical Extraction and Report

Question hence, any similar experiences, clues on this or actual
minimal Perl version requirements I maybe missed?

Thanks,
R.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

[Tobias Oetiker-3]

Hi Raimund,

is your webserver running on the same machine as you tested the
commandline version ? The layer of code that is different between
the perl and the cli version is really small, ...

Are you sure RRDs is picking up the new modules, or cold it be that
it still goes for the 1.2 code ?

cheers
tobi





Today Raimund Berger wrote:

>
> Hi guys
>
> as noted earlier, I recently installed rrdtool 1.3 on a Debian Etch
> server, and after upgrading libcairo everything went fine from build
> to rrdtool execution and performance on the command line.
>
> I now tried some graphing with a couple of perl scripts using RRDs, in
> and out of Apache, and things were deadly slow compared to command
> line performance. Some perl profiling showed that the extra time is
> actually spent in RRDs.
>
> Glancing over the list, I've seen that at least one major patch has
> been applied which might be hard to swallow for Etch's default Perl
> install, the version being:
>
> $ dpkg -l perl
> ii  perl  5.8.8-7etch3   Larry Wall's Practical Extraction and Report
>
> Question hence, any similar experiences, clues on this or actual
> minimal Perl version requirements I maybe missed?
>
> Thanks,
> R.
>
> _______________________________________________
> rrd-users mailing list
> rrd-users@...
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>
>

--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch tobi@... ++41 62 775 9902

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

[Raimund Berger]

Tobias Oetiker <tobi@...> writes:

> Hi Raimund,
>
> is your webserver running on the same machine as you tested the
> commandline version ? The layer of code that is different between
> the perl and the cli version is really small, ...
>
> Are you sure RRDs is picking up the new modules, or cold it be that
> it still goes for the 1.2 code ?

I forced the version in perl with "use RRDs 1.3000" and "1.2015"
directives respectively, and additionally checked correct linkage of
each of the RRDs.so modules with "ldd".

After some further testing I'm bound to correct myself though. The
real bad performance seems to happen only when running in Apache, for
reasons not yet obvious to me. The version switch outlined above makes
a tenfold difference in running time.

Anyway, this is clearly out of the scope of this list. Sorry for the
false alarm, and many thanks for your feedback and those reminders
... ;)

R.

_______________________________________________
rrd-users mailing list
rrd-users@...
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users