From: Shannon Reis <sreis@fastlane.net>
You can also think about it this way:
It takes you exactly 60 minutes to travel 35 miles to work (an average speed of
35 miles/hour). RRD would graph this the hour average as 35 miles/hour for the
hour period (on a daily graph). However, during your drive, you approach the
speed of 80 miles/hour (don't let the cops catch you), and it just so happens
that RRD polled you when you got to the 80mph speed. So, the MAX for that period
would be 80 Miles/hour. Over time, RRD would still save the MAX of 80 Miles/hour
for the day...but it would average out the 35mph to 1.5mph (assuming you didn't
travel at all for the rest of the day).
Basically, what you can extrapolate from this is:
Averages will tell you how much of the available bandwidth was utilized during
the period of time.
Maxes will tell you the maximum amount of available bandwidth was utilized at any
one time during a period of time.
Use averages in relation to MAX's.
For network utilization, it is very helpful to see that your pipe does max out
during peak times during the day, but that over time it utilizes about, say 30%
of the pipe. For network utilization, it is quite common for you to get a MAX
that approaches the bandwidth (even though its usually a 5 minute average'd MAX
-- depending on your polling time). And, and average that is 20-30% of the
total. Network traffic tends to be bursty (especially on LAN's)
For modem utilization, use averages, but mostly focus on the max's because if
your max is at your capacity, you have busy signals! (ie unhappy customers)
There are some cases where MIN's could be usable....but I can't think of them now
;)
Shannon
"Berg, Ivan" wrote:
> From: "Berg, Ivan" <iberg@montana.edu>
>
>
> Probably because cricket averages the longer time periods.
> Notice your average for the day is about half what your peak value is. This
> average is what you seeing in the long run(you lose specifics in the long
> run but gain a better idea of the average picture is)
>
> -----Original Message-----
> From: Aurelio Sanchez
> To: cricket-users@onelist.com
> Sent: 10/5/99 3:54 PM
> Subject: [cricket-users] Yearly graph
>
> From: Aurelio Sanchez <asanchez@avantel.net.mx>
>
> Hi!
>
> I'm using crickte 0.70 with rrdtool 1.07 in a ultra 1 with solaris
> 2.6. Currently I have a DS3 link been graphicated and I'm noticing
> something really wierd.
>
> The hourly graph shows the link almost full. The summary is as follows:
>
> Summary
>
> Values at last update:
> Average bits in (for the day):
> Cur: 39.36 Mbits/sec
> Avg: 25.41 Mbits/sec
> Max: 41.17 Mbits/sec
> Average bits out (for the day):
> Cur: 8.84 Mbits/sec
> Avg: 5.88 Mbits/sec
> Max: 10.04 Mbits/sec
>
> Last updated at Tue Oct 5 16:45:09 1999
>
> However my yearly graph shows the link barely half full and this data
> is not making any sense to my upper management. Can anybody explain me
> why is thios behaviour?, is this correct and I not understanding the
> graphs?
>
> Any help will be appreciated.
>
> Thanks,
>
> Aurelio Sanchez
>
>
--------------------------- ONElist Sponsor ----------------------------
Does Windows keep ""bugging"" you? Can't get that PowerPoint slide to fit?
Get FREE real-time live expert support over the Internet at expertcity.com.
<a href=" http://clickme.onelist.com/ad/expertcity7 ">Click Here</a>
------------------------------------------------------------------------
This archive was generated by hypermail 2b29 : Mon Mar 06 2000 - 19:01:03 PST