<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [smokeping-users] Smokeping performance tracking</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Courier New">Tobi,</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">there is significant performane to be gained by having sufficient<BR>
</FONT><FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">cache on your box so that all active rrds stay n cache ... in<BR>
</FONT><FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">rrdtool 1.3 we did some work to reduce the 'pre rrd' cache<BR>
</FONT><FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">requirements …</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">We are going to look at deploying smokeping to a servers that have San access so I guess diskio problems should be less of an issue but I will look at what performance gain we can get from rrdtool 1.3</FONT><BR>
<BR>
<FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">if rrdtool does not finisch a round of updating in time, it will<BR>
</FONT><FONT SIZE=2 FACE="Courier New">></FONT><FONT SIZE=2 FACE="Courier New">say so in its logs …</FONT>
</P>
<P><FONT SIZE=2 FACE="Courier New">We have seen this in the log but this really only provides a reactive way to know you have a capacity problem it would be much nicer to see it coming rather than waiting for it to happen.</FONT><BR>
<BR>
<FONT SIZE=2 FACE="Courier New">Regards</FONT>
<BR><FONT SIZE=2 FACE="Courier New">JonG</FONT>
</P>
<br clear=all> The information contained in this e-mail and its attachments is confidential.
It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent.
</BODY>
</HTML>