headers
Tobias Oetiker | 7 Jun 2009 17:37
Picon
Gravatar

RRDtool 1.4rc1 with RRDcached performance accelerator

After some more work on the build process, I have put out

  RRDtool 1.4 RC1

it is a copy of the current trunk snapshot

  http://oss.oetiker.ch/rrdtool/pub/beta/rrdtool-1.4rc1.tar.gz

Please test this on the platform of your choice and report any
problems you find to

  http://oss.oetiker.ch/rrdtool-trac/newticket

Below you find the NEWS file for 1.4. If you have any additions,
please tell me.

News for RRDtool 1.4
====================
$Id: NEWS 1840 2009-06-07 11:16:07Z oetiker $

RRD Caching Daemon (rrdcached)
------------------------------
by Florian Forster and Kevin Brintnall

The RRD Caching Daemon can dramatically improve the 'update' performance
of your system.  Due to filehandling overheads, the time it takes todo one
update is virtually the same as to doing two updates in a row.

The Cache Daemon intercepts rrdtool update calls, assembling multiple
updates before writing them to the actual rrd file. When calling rrdtool
(Continue reading)

Permalink | Reply |
headers
Fidelis Assis | 8 Jun 2009 02:57
Picon
Favicon

Re: RRDtool 1.4rc1 with RRDcached performance accelerator

Tobias Oetiker escreveu:
> After some more work on the build process, I have put out
> 
>   RRDtool 1.4 RC1

After applying the missing patches pointed out by Kevin it compiled OK.
Lua bindings also worked OK - make test generated the graph as expected.

--

-- 
Fidelis
Permalink | Reply |
headers
kevin brintnall | 8 Jun 2009 00:57

build tool-chain updates (was: 1.4rc1 announcement)

> * switched to using automake 1.11 which provides a 'silent' build process,
>   causing errors and warnings to stand out much more than before.
>   by Tobi Oetiker

Tobi,

Are all these version upgrades necessary?  I think we should only insist
on the minimum version required to correctly build the software.

-LIBTOOL_VER="1.5.6"
+LIBTOOL_VER="2.2.6"

1.5.6 continues to build rrdtool correctly on my system...

-AUTOMAKE_VER="1.9.2"
+AUTOMAKE_VER="1.11"

The new version is only 3 weeks old.. unlikely to be picked up by
packagers.  I can still build correctly under 1.9.2.

-AUTOCONF_VER="2.59"
+AUTOCONF_VER="2.63"

I like 'AC_USE_SYSTEM_EXTENSIONS', available since 2.60.  But, everything
still builds correctly on 2.60.  Is it worth forcing this feature or can
we conditionally enable it?

If there are other reasons that make the forced upgrade worthwhile, can
you elaborate?
(Continue reading)

Permalink | Reply |
headers
Tobias Oetiker | 8 Jun 2009 06:51
Picon
Gravatar

Re: [rrd] build tool-chain updates (was: 1.4rc1 announcement)

Hi Kevin,

Yesterday kevin brintnall wrote:

> > * switched to using automake 1.11 which provides a 'silent' build process,
> >   causing errors and warnings to stand out much more than before.
> >   by Tobi Oetiker
>
> Tobi,
>
> Are all these version upgrades necessary?  I think we should only insist
> on the minimum version required to correctly build the software.
>
> -LIBTOOL_VER="1.5.6"
> +LIBTOOL_VER="2.2.6"
>
> 1.5.6 continues to build rrdtool correctly on my system...
>
> -AUTOMAKE_VER="1.9.2"
> +AUTOMAKE_VER="1.11"
>
> The new version is only 3 weeks old.. unlikely to be picked up by
> packagers.  I can still build correctly under 1.9.2.
>
> -AUTOCONF_VER="2.59"
> +AUTOCONF_VER="2.63"
>
> I like 'AC_USE_SYSTEM_EXTENSIONS', available since 2.60.  But, everything
> still builds correctly on 2.60.  Is it worth forcing this feature or can
> we conditionally enable it?
(Continue reading)

Permalink | Reply |

Gmane